On Feb 17, 2006, at 11:47 AM, Rick Morrision wrote:
You mean you can't do an INSERT on this table with SA? A strawman use case, sure -- but shouldn't we be able to handle it?
theres no reason it cant handle it, and I can just take out the particular error message giving the problem/insure that it works, in the case theres no way for it to get a handle on the last inserted row.....the error condition would move up to the ORM level when it inserts a new object (because an ORM needs rows with unique primary keys, and it needs to know what row was just inserted). its the way it is now, i.e. across the board even when not needed, more as a test case/simpler starting point.
------------------------------------------------------- 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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Sqlalchemy-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
