I think we know why it is happening and you are right, it is associated with ALTER TABLE. What I think is happening is this: we are using dbdeploy to upgrade our schemas at startup. The alter table causes a new table (TEMP_TABLE_4) to be created, and then deletes the old table and renames the temp table to replace it. Later (in tests) we do a "DELETE FROM..." and that query seems to not notice that the old table is renamed and uses the old name (TEMP_TABLE_X)
I can try and do a test case for you if you can't work it out from that. I won't be able to get to it for a couple of days though. chris On Wed, Oct 1, 2008 at 1:21 PM, Thomas Mueller <[EMAIL PROTECTED] > wrote: > > Hi, > > > we are seeing this error when trying to clear out our tables at the > > end of a test run. Has anyone seen this before and have a fix for it? > > This sounds like a bug, maybe related to ALTER TABLE. Is it possible > to post a simple test case? If that is not possible, could you append > ;TRACE_LEVEL_FILE=3 to the database URL and run the test again please? > This will write all JDBC calls and SQL statements to the *.trace.db > file. If you send me or post this file I can then re-run the test and > find out what the problem is. > > Regards, > Thomas > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
