0.5rc4 is out, I wanted to get it out quickly since people were  
hitting a garbage-collection bug that was introduced in 0.5rc3.   I'm  
using rc4 on a production site right now so I'm pretty confident that  
it's quite solid and hopefully I won't start changing more things  
before an 0.5.0 final.

This is also the best performing SQLA we've had to date.  Expect a tad  
more pep in your applications :).

Download SQLAlchemy 0.5rc4 at:  http://www.sqlalchemy.org/download.html


0.5.0rc4
========
- features
- orm
     - Query.count() has been enhanced to do the "right
       thing" in a wider variety of cases. It can now
       count multiple-entity queries, as well as
       column-based queries. Note that this means if you
       say query(A, B).count() without any joining
       criterion, it's going to count the cartesian
       product of A*B. Any query which is against
       column-based entities will automatically issue
       "SELECT count(1) FROM (SELECT...)" so that the
       real rowcount is returned, meaning a query such as
       query(func.count(A.name)).count() will return a value of
       one, since that query would return one row.

     - Lots of performance tuning.  A rough guesstimate
       over various ORM operations places it 10% faster
       over 0.5.0rc3, 25-30% over 0.4.8.

- bugfixes and behavioral changes
- general:
     - global "propigate"->"propagate" change.

- orm
     - Adjustments to the enhanced garbage collection on
       InstanceState to better guard against errors due
       to lost state.

     - Query.get() returns a more informative
       error message when executed against multiple entities.
       [ticket:1220]

     - Restored NotImplementedError on Cls.relation.in_()
       [ticket:1140] [ticket:1221]

     - Fixed PendingDeprecationWarning involving order_by
       parameter on relation(). [ticket:1226]

- sql
     - Removed the 'properties' attribute of the
       Connection object, Connection.info should be used.

     - Restored "active rowcount" fetch before ResultProxy
       autocloses the cursor.  This was removed in 0.5rc3.

     - Rearranged the `load_dialect_impl()` method in
       `TypeDecorator` such that it will take effect
       even if the user-defined `TypeDecorator` uses
       another `TypeDecorator` as its impl.

- access
     - Added support for Currency type.

     - Functions were not return their result. [ticket:1017]

     - Corrected problem with joins. Access only support
       LEFT OUTER or INNER not just JOIN by itself.
       [ticket:1017]

- mssql
     - Lots of cleanup and fixes to correct problems with
       limit and offset.

     - Correct situation where subqueries as part of a
       binary expression need to be translated to use the
       IN and NOT IN syntax.

     - Fixed E Notation issue that prevented the ability to
       insert decimal values less than 1E-6. [ticket:1216]

     - Corrected problems with reflection when dealing with
       schemas, particularly when those schemas are the
       default schema. [ticket:1217]

     - Corrected problem with casting a zero length item to
       a varchar. It now correctly adjusts the CAST.

- ext
     - Can now use a custom "inherit_condition" in
       __mapper_args__ when using declarative.


--~--~---------~--~----~------------~-------~--~----~
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