Then really looks like a bug to me. Please file an issue here: https://github.com/h2database/h2database/issues
Sergi 2016-09-08 0:01 GMT+03:00 ck <[email protected]>: > Hello, thanks for your help > > DEFAULT NOW() -> Updates when row is added to current timestamp > AS NOW() -> Updates the row to current timestamp whenever the row is > added/updated > > In my case I am storying a 'EDIT_TIME' COL, and then I need to auto update > to latest timestamp all the time the row is updated > so I cannot use DEFAULT in this case. > > Any solution to my issue? > Seriously, you should take this in consideration. I am stuck with a > production database unrestorable because of this nasty COL. > > I can't think nobody ever mentioned this kind of behavior, it seems a > pretty common use case for me. > So be careful to everyone restoring the database If you didn't think of > this before > > -- > 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 https://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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
