Hi,
I encountered a rather strange situation.
A trigger that has a select was internally being cached somehow and
lingered on.
I had changed the select and the old select caused an error as part of a
merge statement.
I deleted all objects from the database and recreated it.
But somehow the old select lingered on.
I rebooted and tried everything but I could not get rid of the ghost select.
Only deleting the db file, creating a new one and then creating the
database objects got rid of it.
I don't have a test case but I would guess that some data about the db
objects is kept internally somewhere
and can stick around if the same names are used when db objects are
recreated.
Using the latest version with MV_STORE and MVCC.
- Rami
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
