> > I suggest to create a new database with a different collation, and then > migrate the data. >
That's harder than you think because the database is used onsite at the customer... > > > a) Permit connection to a database even if the collation is different > and can not be updated > > That wouldn't work properly. Indexes are sorted depending on the > collation, so queries wouldn't return the correct result. > What I meant was that you would just accept the connection and open the database even if the collation that was set in the connection string was wrong. Just run on the collation that the database is set to. > > b) Add a feature that enables H2 to update the collation > > This would mean "automatic migration". This doesn't need to be done inside > the database engine itself. I think it can be done purely on top of the > database, using the existing features "script" and "runscript". > Well other database engines are capable of doing that... -- 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.
