Hi Thomas, This should work. Is this available today? We are currently using 1.3.175
The issue we'll be encountering is that database close jdbc call still have an open file handle and we cannot override copy the backup we took. Thanks, Meni On Tue, Jan 13, 2015 at 10:48 PM, Thomas Mueller < [email protected]> wrote: > Hi, > > I'm afraid this can't be fixed easily in the next future. What could be > done (with the MVStore, so that's only version 1.4.x) is to create a > database wide "marker checkpoint" that allows you to roll back to it if > needed. Manual rollback would probably require to re-open the database. It > could be used as follows (admin only): > > // list existing checkpoints > Statement.executeUpdate("select * from information_schema.checkpoints"); > > // create a checkpoint named "version 1" > Statement.executeUpdate("checkpoint mark 'version 1'"); > > // ... then do the schema changes ... > > // either: remove the checkpoint > Statement.executeUpdate("checkpoint remove 'version 1'"); > > // ... or rollback to that checkpoint (this will close the database; you > will need to re-open it) > Statement.executeUpdate("checkpoint rollback 'version 1'"); > > This feature would be somewhat related to "point in time recovery", for > example as described here: > http://www.postgresql.org/docs/9.1/static/continuous-archiving.html > > Regards, > Thomas > > > On Sunday, December 21, 2014, Meni Hillel <[email protected]> wrote: > >> I have the same issue. I saw no where in the documentation that this is >> the behavior. This is quite severe in my opinion. We have an schema upgrade >> framework that involved from DDL and DML commands. To move from one schema >> version to another, you mass perform all steps successfully or non at all. >> >> When will this be fixed? >> >> On Wednesday, March 30, 2011 10:38:13 AM UTC-7, Thomas Mueller wrote: >>> >>> Hi, >>> >>> > It seems that ddl-statements are out of >>> > the transaction and couldn't be rolled back. >>> >>> Yes, this is a known and documented limitation. I will increase the >>> priority, but will not fix it currently. >>> >>> Regards, >>> Thomas >>> >>> -- >> 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. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "H2 Database" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/h2-database/BiHZeFQoCpI/unsubscribe. > To unsubscribe from this group and all its topics, 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. > -- 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.
