the "uniquing" logic is only enabled when you query for mapped entities, not individual columns, so from the Query the option would be to only query for individual columns.
Query could be modified to allow a disabling option, though I wonder why exactly you'd need duplicate instances back. On Aug 6, 2012, at 6:16 PM, kris wrote: > Well.. I can certainly understand why it's needed, but in my case I actually > need to receive the two > duplicate instances. > Is there any way to remove this de-duplicate behavior or work around? > > > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/sqlalchemy/-/bGlkp8JDtBQJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/sqlalchemy?hl=en. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
