Version 1.2.143 contained the following change: "If the user name and password are not set or empty, then the password is not hashed. To disable this behavior, set the system property h2.emptyPassword to false."
As a consequence, setting the above mentioned system property seems to be required in order to open existing databases with empty user name and/or password. Wouldn't it be better to let the default behavior be what it used to be, and then use the system property to deviate from that if needed? Or is there an obvious way to migrate existing (embedded) databases with empty credentials to comply with the new behavior? I would like to keep my H2 up do date, but messing with system properties feels somewhat fragile. Thanks, Joonas -- 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.
