On Jul 12, 2011, at 2:30 PM, Krishnakant Mane wrote: > On 12/07/11 23:36, Michael Bayer wrote: >> On Jul 12, 2011, at 1:57 PM, Krishnakant Mane wrote: >> >>> On 12/07/11 20:34, Michael Bayer wrote: >>>> Hi Krishnakant - >>>> >>>> 0.7.1 is the current stable production release which is where the focus of >>>> development also lies. 0.6 is in maintenance releases at this point. >>> >>> In that case will I have to change my code if I want to shift from 0.6 to >>> 0.7? >>> I use Pylons as my web application framework. >>> In addition the major projecct I am working on is using sqlalchemy version >>> 0.6.3 in its core engine. >>> The core engine sends and recieves xml rpc messages. >>> It then uses sqlalchemy to talk with the database in postgresql. >>> I plan to use a lot of expression api so I will like to know overall what >>> all changes will i have to make in my code which uses 0.6. >>> Happy hacking. >>> Krishnakant. >> if you're on 0.6, you'd move up to 0.6.8 to get the latest fixes and such, >> and you can stay on 0.6 for the time being. >> >> Moving to 0.7 requires little to no changes to calling code. But you >> would need to fully test your 0.6 application on 0.7 before moving into >> production. There are very few backwards incompatible changes overall, >> details at http://www.sqlalchemy.org/trac/wiki/07Migration > > So is 0.6.8 updated with the performance bennifits that we get in 0.7?
no it's not, by "latest fixes" i meant bugfixes that have been identified as back-portable to 0.7, which have been many, but generally do not include performance enhancements which are based on deeper architectural changes. -- 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.
