Gaetan de Menten wrote: > > Hi Mike, > > I see in r6413, that you use an ordered dictionary instead of a > standard one for properties, in an attempt to "fix some jython > ordering annoyingness". Is this really necessary to be compliant with > Jython? Would you care to explain? I'm quite puzzled as to how that > change could have any effect...
that particular odict is only within the context of a particular unit test which is looking for an exact SQL statement to be rendered based on that mapper. the depending on the order of the "address" and "orders" attribute (if i recall correctly the names), its the difference between: select address.foo, address.bar, orders.foo, orders.bar, ... and select orders.foo, orders.bar, address.foo, address.bar, ... i.e. it doesn't make any difference except for a test that is testing for an exact SQL string. dictionary ordering changes based on platform and implementation. In this case those two attributes got reversed when run on Jython. the mapper's internal dictionary of properties is ordered in any case, in this case its just the dictionary used to pass the argument in within the test. > > Thanks in advance, > -- > Gaëtan de Menten > http://openhex.org > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
