I suggested that the message writes to stderr and/or stdout. I know that's pretty poor, and often useless, but I can't think of a better option, and it *might* point some users in the right direction.
"In theory, old clients should work with new server (and vice-versa)". Indeed. Meanwhile, back in the real world, there do seem to be many issues raised on this list that are resolved by getting the version of the client and the engine aligned. Do you think this is just a short-term problem? Just a thought that might help a little. Cheers Kerry On Mon, Mar 8, 2010 at 7:13 AM, Thomas Mueller <[email protected] > wrote: > Hi, > > > If the version number of the database files doesn't match the version > number > > of the code that is connecting to the engine, then perhaps H2 should > display > > a warning message (because this mismatch seems to be a common cause of > > problems for users) > > That's one option, however where should it display the warning? > > In theory, old clients should work with new server (and vice-versa), > but the problem was that there was no test case for that. Now there is > such a test case (using a custom classloader). > > Regards, > Thomas > > -- > 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]<h2-database%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/h2-database?hl=en. > > -- 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.
