This may not be a bug per-se, but definitely isn't the behavior I expected. The issue in a nutshell is: when you rename the public schema to something else and create a new public schema, and the original public schema contained a sequence, then the database file will be corrupted somehow.
Steps to reproduce: 1. Connect to database, don't change schema so you'll be using the public schema. 2. Execute: CREATE SEQUENCE demo_sequence; 3. Execute: ALTER SCHEMA public RENAME TO demo_schema; 4. Execute: CREATE SCHEMA public; 5. Disconnect from the database. 6. Attempt to reconnect to the database. You'll see a message to the effect of: Exception in thread "main" org.h2.jdbc.JdbcSQLException: Schema "DEMO_SCHEMA" not found -- 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.
