I'm afraid that there really isn't very much we can once the DB is
corrupted.
The Recover tool is very much a Hail Mary pass, a last-ditch effort.
Your best bet is probably to reconstruct your schema using your own
code, and then use chunks of the script that the Recover tool generated
to import as much data as it feasible.
Oh yes, and create a backup procedure for your DB's so you don't have to
go through this again :-)
http://h2database.com/html/tutorial.html#upgrade_backup_restore
http://h2database.com/javadoc/org/h2/tools/Backup.htm
On 2013-08-20 03:25, Matthew Lohbihler wrote:
If by chance you might be interested in making the recover tool a bit
more magic than it already is, i can provide the database off-line of
this conversation. At the moment, having it recover to SQL that is not
usable makes the recovery tool of dubious value. I can try to fix the
SQL as you say, but it is certainly not of the standard "alter table"
type that i'm used to. I'd need a Getting Started guide to understand
why it does things the way it does.
"... but make sure to keep the one with the highest start value"
In fact, all of the duplicate entries are duplicates; they all have
the same start value.
--
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/groups/opt_out.
