Bug 292 : Deep query with fetch claues out of order can miss a +query join (Autofetch can do this)
Priority 
High
Reported Version 
 
Logged By 
Rob
Status 
Fixed
Fixed Version 
2.6.0
Assigned To 
 
Product 
Ebean - core
Duplicate Of 
 
Created 
08/05/2010
Updated 
08/05/2010
Type 
Bug
 
Attachments 
No attachments

So the fetch clauses are expected to be in order:

So if they are out of order like:

find order
fetch customer.contacts.notes
fetch customer.contacts
fetch customer

rather than:

find order
fetch customer
fetch customer.contacts
fetch customer.contacts.notes

Then Ebean can assign a "query join" incorrectly (to customer.contacts.notes rather than customer.contacts in this case).

Ebean should handle this by ordering the fetch paths if required.

 
woResponse

Upload a file