..coincidentally released on the self-same day when I am finally taking the wraps off 0.4.0 for a spin on a new project.
Congrats on this huge release, everybody! On 10/17/07, Michael Bayer <[EMAIL PROTECTED]> wrote: > > > Hey list - > > I'm very happy to announce that we've put out 0.4.0 final. Thanks > to all the contributors as well as all the beta testers who have > helped us move through six beta releases, just to make sure we've got > everything right (or as much right as we can). For those still > working with 0.3, its time to upgrade ! :) Lots of folks have > already done it and it's not so hard. I think this is the most well > documented and easy to use SQLAlchemy yet, and its definitely the > fastest by a wide margin...many kinds of operations are 50% faster > and the large majority of applications should be at least 20-30% > faster. We now have hotspot profiling tests as part of our > testsuite so that performance-reducing changes immediately raise red > flags (and of course, performance-increasing changes unleash a shower > of balloons....). > > Of course, 0.4 is a lot more than just an internal refactoring > release - the public facing side also shifts the paradigms up another > notch or two. The Whats New document (http://www.sqlalchemy.org/trac/ > wiki/WhatsNewIn04 ) has been tracking all the enhancements and > changes. The emphasis is on reduced complexity and increased > flexibility, including a very consistent Query object as well as a > generative select() construct, far better integration of explicit > transactions with engines and sessions, and mappers that are much > smarter about multi-table and inheritance mappings. We've also > addressed a lot of the framework integration confusion and produced > patterns and helpers that standardize web framework integration..not > as plugins but as core features. > > The changelog documents 0.4 on a beta-by-beta basis. Big changes > since 0.4.0beta6 include an experimental Sybase driver, as well as a > new in_() syntax which standardizes on being passed a list rather > than *args (i.e. in_([1,2,3]) instead of in_(1,2,3)). The old way > still works of course but is deprecated. > > 0.4 download: http://www.sqlalchemy.org/download.html > documentation/migration overview (worth a read): http:// > www.sqlalchemy.org/docs/04/intro.html > > - mike > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
