Hello again !

This is a bugfix release and is recommended for all users who are  
currently on 0.4.2 or 0.4.2a.   There is one critical bugfix which  
involves history calculation on collection-based attributes.  Other  
significant bugfixes include a potential error that can arise with  
"delete-orphan" cascade, a fix to synonym() regarding backrefs, some  
more advanced collections behavior fixes, a datetime-related fix to  
the MSSQL dialects, and a fix for the the "order_by(None)" call which  
can be used on a select() object in order to clear the criterion.

Also, we just released two days ago and the changelog already has 11  
new items.  Geez !

download the latest and greatest at:  http://www.sqlalchemy.org/download.html


0.4.2b
------
- sql
     - changed name of TEXT to Text since its a "generic" type; TEXT  
name is
       deprecated until 0.5.  The "upgrading" behavior of String to Text
       when no length is present is also deprecated until 0.5; will  
issue a
       warning when used for CREATE TABLE statements (String with no  
length
       for SQL expression purposes is still fine) [ticket:912]

     - generative select.order_by(None) / group_by(None) was not  
managing to
       reset order by/group by criterion, fixed [ticket:924]

- orm
     - suppressing *all* errors in InstanceState.__cleanup() now.

     - fixed an attribute history bug whereby assigning a new collection
       to a collection-based attribute which already had pending changes
       would generate incorrect history [ticket:922]

     - fixed delete-orphan cascade bug whereby setting the same
       object twice to a scalar attribute could log it as an orphan
       [ticket:925]

     - Fixed cascades on a += assignment to a list-based relation.

     - synonyms can now be created against props that don't exist yet,
       which are later added via add_property().  This commonly includes
       backrefs. (i.e. you can make synonyms for backrefs without
       worrying about the order of operations) [ticket:919]

     - fixed bug which could occur with polymorphic "union" mapper
       which falls back to "deferred" loading of inheriting tables

     - the "columns" collection on a mapper/mapped class (i.e. 'c')
       is against the mapped table, not the select_table in the
       case of polymorphic "union" loading (this shouldn't be
       noticeable).

- ext
     - '+', '*', '+=' and '*=' support for association proxied lists.

- dialects
     - mssql - narrowed down the test for "date"/"datetime" in MSDate/
       MSDateTime subclasses so that incoming "datetime" objects don't
       get mis-interpreted as "date" objects and vice versa, [ticket: 
923]


--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to