Oliver Stabel wrote : >Hello,
>I have a table with a key defined as SERIAL(1). During the import of data I >realized >that I had to extend one field. I therefore used SQL Studio to alter the >table and >changed the required field (not the key field). >Now, inserting new entries into the table gives me the following error: >[SAP AG][SQLOD32 DLL][SAP DB]Integrity constraint violation;200 POS(1) >Duplicate key. >There seems to be a similar problem here: >http://listserv.sap.com/pipermail/sapdb.general/2002-February/010603.html >I am using Kernel 7.4.3 Build 017-123-039-277 and Windows XP. >My questions are: >- does ALTER TABLE reset the SERIAL value for a table? yes, it does, but this is a bug. We will fix it as soon a possible >- where can I check the current value (besides <table>.currvalue after an >INSERT?) and can there's no other way > I change it? no Regards, Thomas -- Thomas Anhaus SAP DB, SAP Labs Berlin [EMAIL PROTECTED] http://www.sapdb.org/ _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
