Getting rid of the auto-magic IDENTITY_INSERT on/off should be easy, but it will make several basic unit tests fail -- maybe making that behavior switchable w/b better?
Rick
On 9/11/06, Michael Bayer <[EMAIL PROTECTED]> wrote:
On Sep 10, 2006, at 9:55 PM, Rick Morrison wrote:
> Oh, it gets even better. You can only have IDENTITY_INSERT on for
> one table at a time. Trying to set it on for another table while it
> is set on elsewhere will throw an error. It is necessary to turn it
> off first, then set it on for the other table.
>
Ok the "IDENTITY_INSERT" is only when you are inserting an *explicit*
value into an IDENTITY column, right ? i would rather just allow
users to choose IDENTITY or not, using a flag on Column such as
"autoincrement=True". obviously it defaults to True right now, but
for databases that cant handle switching (like ms-sql), you can turn
it off and get a non-IDENTITY column. lets take that SET
IDENTITY_INSERT stuff out, thats not going to scale at all; it
appears that its intended for batch loads and isnt really appropriate
within an application flow.
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
