Hi, > 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.
I would like to avoid that. I think it's bad style if a library writes to stderr / stdout. > 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? I hope so, yes. The main problem was that this use case was not tested. Having automated tests should catch problems in the future. 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]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
