Re: Default collection class for unordered relations

> After looking over the 0.5 migration notes and seeing that implicit
> ordering is to be removed, it seems to me that it might make sense
> to change the default collection class for unordered relations from
> a list to a multiset.  This would reinforce that unless order_by is
> specified, one cannot rely on a collection having a particular
> order. I could see this as helpful in preventing bugs when
> switching between databases (e.g. from MySQL to PostgreSQL) with
> different default ordering behaviors.
mmh. between db's - maybe u're right. But the order will also change 
depending on current hash-values between 2 runs on otherwise same 
system... There's plenty of difficulties to get a repeatable flow for 
tests etc already.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sqlalchemy" group.
To post to this group, send email to sqlalchemy <at> googlegroups.com
To unsubscribe from this group, send email to sqlalchemy-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---