Codename for SQLAlchemy 0.4 beta5: "Better than beta4."
Beta4 introduced a small connection pool glitch which we fixed within a few revisions of that release (yes its the "too many connections" issue you're all getting), so its recommended everyone on beta4 upgrade to beta5 (unless of course, some other disastrous bug is introduced in beta5....but I think we're good :) ). With this release, im hoping that this one starts to "feel" lighter and quicker (I've already heard that comment made) - we are really cutting down on the CPU cycles and method calls. We have fully 27-45% fewer method calls across all of the infamous Geniusql performance tests based on the version those were probably made against. Big changes in particular with insert/update SQL default expressions, which now execute "inlined" in most cases, and the "pre- execute" defaults like Postgres and Oracle sequences execute at a lower level so theres much less overhead on those too. download at: http://www.sqlalchemy.org/download.html where you'll notice i dont even have beta4 listed due to the stability issue. more to come of course ! changes: 0.4.0beta5 ---------- - connection pool fixes; the better performance of beta4 remains but fixes "connection overflow" and other bugs which were present (like [ticket:754]) - fixed bugs in determining proper sync clauses from custom inherit conditions [ticket:769] - Extended 'engine_from_config' coercion for QueuePool size / overflow. [ticket:763] - mysql views can be reflected again. [ticket:748] - AssociationProxy can now take custom getters and setters. - Fixed malfunctioning BETWEEN in orm queries. - Fixed OrderedProperties pickling [ticket:762] - SQL-expression defaults and sequences now execute "inline" for all non-primary key columns during an INSERT or UPDATE, and for all columns during an executemany()-style call. inline=True flag on any insert/update statement also forces the same behavior with a single execute(). result.postfetch_cols() is a collection of columns for which the previous single insert or update statement contained a SQL-side default expression. - fixed PG executemany() behavior, [ticket:759] - postgres reflects tables with autoincrement=False for primary key columns which have no defaults. - postgres no longer wraps executemany() with individual execute() calls, instead favoring performance. "rowcount"/"concurrency" checks with deleted items (which use executemany) are disabled with PG since psycopg2 does not report proper rowcount for executemany(). - Tickets fixed: - [ticket:742] - [ticket:748] - [ticket:760] - [ticket:762] - [ticket:763] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
