Michael Bayer wrote:
It seems though, that you are looking for some kind of update/delete/
insert at the mapper level. While I could add a more 'mapper'-ized
version of the above methods to the mapper, it would be a feature that
is inherently broken, since if the mapper just uses straight updates
and deletes to modify things, it has no way to update dependent
objects, or of knowing if its going to violate constraints if it cant
load all the corresponding data into memory. it doesnt have the
ability to aggregate stuff like that into additional en- masse queries.
although i suppose its possible to add such a feature since it knows
the general dependency relationships. it would be a large undertaking
probably better left after this thing has some releases going.
Well, I am not necessarily *looking* for that, but merely asking. Just
wanting to clarify for me if you use a mapper, what you should use the
mapper for, and when to use straight table stuff.
Thankyou! It is more clear now....
David
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Sqlalchemy-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
