nearing the end of the 0.1 series, as some major reorganization is going
on for the 0.2 series.  0.2 will be mostly backwards compatible, but some
code might need some name changes so the 0.1 series will still be
available.

changes for 0.1.6:

0.1.6
- support for MS-SQL added courtesy Rick Morrison, Runar Petursson
- the latest SQLSoup from J. Ellis
- ActiveMapper has preliminary support for inheritance (Jeff Watkins)
- added a "mods" system which allows pluggable modules that modify/augment
core functionality, using the function "install_mods(*modnames)".
- added the first "mod", SelectResults, which modifies mapper selects to
return generators that turn ranges into LIMIT/OFFSET queries (Jonas
Borgström)
- factored out querying capabilities of Mapper into a separate Query object
which is Session-centric.  this improves the performance of
mapper.using(session)
and makes other things possible.
- objectstore/Session refactored, the official way to save objects is now
via the flush() method.  The begin/commit functionality of Session is
factored
into LegacySession which is still established as the default behavior, until
the 0.2 series.
- types system is bound to an engine at query compile time, not schema
construction time.  this simplifies the types system as well as the
ProxyEngine.
- added 'version_id' keyword argument to mapper. this keyword should
reference a
Column object with type Integer, preferably non-nullable, which will be
used on
the mapped table to track version numbers. this number is incremented on each
save operation and is specifed in the UPDATE/DELETE conditions so that it
factors into the returned row count, which results in a ConcurrencyError
if the
value received is not the expected count.
- added 'entity_name' keyword argument to mapper. a mapper is now associated
with a class via the class object as well as an optional entity_name
parameter,
which is a string defaulting to None. any number of primary mappers can be
created for a class, qualified by the entity name. instances of those classes
will issue all of their load and save operations through their
entity_name-qualified mapper, and maintain separate a identity in the
identity
map for an otherwise equilvalent object.
- overhaul to the attributes system. code has been clarified, and also
fixed to
support proper polymorphic behavior on object attributes.
- added "for_update" flag to Select objects
- some fixes for backrefs
- fix for postgres1 DateTime type
- documentation pages mostly switched over to Markdown syntax



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
Sqlalchemy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users

Reply via email to