a few fixes i wanted to get out the door. the passive_deletes flag
wasnt working, the "lazy=None" (a.k.a. "noload") strategy was broken
after the 0.3 series, and the recent mysql enhancement of catching
2006/2014 errors was not reraising other OperationalError exceptions.
Also got two terrific user contributions: QueuePool can now properly
recover from a bunch of failed connections, and rowcount now functions
with MySQL (and therefore ORM version checking during a flush, if you
specify version_id_col), utilizing various undocumented MySQLdb API
features.
The "string-based FROM clause" fix means you can now do something like
this:
select([column('col1'), column('col2')], "col1=5",
from_obj=["sometable"])
i.e. constructing a SELECT from individual components, using nothing
but strings (you can even make a read-only mapper against it). this is
what some of you want ! so now you have it.
0.3.3
- string-based FROM clauses fixed, i.e. select(...,
from_obj=["sometext"])
- fixes to passive_deletes flag, lazy=None (noload) flag
- added example/docs for dealing with large collections
- added object_session() method to sqlalchemy namespace
- fixed QueuePool bug whereby its better able to reconnect to a
database
that was not reachable (thanks to Sébastien Lelong), also fixed
dispose()
method
- patch that makes MySQL rowcount work correctly! [ticket:396]
- fix to MySQL catch of 2006/2014 errors to properly re-raise
OperationalError
exception
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
