Hi Ulf, > I'm sorry > i changed the table definition by using the GUI in 3.1.1 on WinXp. > Courios is, that the made changes by default values not exist after > saving and reopening anymore.
This does not happen in CWS dba32g anymore, our last "regular" bug fix CWS towards 3.2, containing all fixes made so far. IIRC, Ocke recently fixed a bug like this. > But the Autoincrement from my primary Key in this table begins after > that at 0 again. The inserted data is not count straight up. I > should have deleted the id 0 before. > > After changing the table definition i could insert exact 1 dataset > with ID 0. After that i can't insert datasets anymore. > > Is this a known bug, or what can i do now, because i use the indexes > in other tables too. Not that you submitted it as issue 104901 (thanks!) it is known :) That looks as if it is a bug in the HSQL engine, nonetheless I hope we will be able to fix it before the 3.2 release (I just nominated it as 3.2 blocker). In the past, I encountered similar problems with auto increment columns (though I think I did not play with default values, but triggered them differently), and IIRC, it helped to open the table, and increment the column value of the last record (i.e. with the greatest value) by 1, and then set it back to its previous value. After this, the auto increment worked, again. Just a workaround, but a better one than 500 failing attempts to insert a new record. Ciao Frank -- - Frank Schönheit, Software Engineer [email protected] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
