On Tue, Aug 11, 2009 at 16:20, [email protected]<[email protected]> wrote:
> I'm using Elixir in a new project and, during unit tests, I hit a > situation that maybe a bug. Before data is flushed, an OneToMany(..., > order_by='<fieldname>') relationship just appends related objects at > the end of the list, ignoring the order_by clause. Only after session > is committed, order_by is respected. This is not a bug, it is the intended behavior. See http://elixir.ematia.de/trac/ticket/91for some details. You might want to create a feature request (it should probably be done trough a new collection implementation on SQLAlchemy's side) on SQLAlchemy's trac if it doesn't exist already. -- Gaëtan de Menten http://openhex.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SQLElixir" 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/sqlelixir?hl=en -~----------~----~----~----~------~----~------~--~---
