Hi all, We use several in-memory H2 databases for different purposes. Some are purely internal for consumption of intermediate results, some are exposed to external tools. They are really independant and there can be multiple databases up at the same time.
For internal consumption, we don't want serialization of Java Objects so we use the new "h2.serializeJavaObject" system property to false. The problem is that we want this property to have an effect on certain of those H2 instances. Shouldn't such property be part of the DbSettings instead? Or shouldn't we consider having 2 distinct types for Java objects? They could be OTHER and OBJECT. That way, we could even have both types in the same database. OTHER would store objects a bit like blobs, OBJECT would have more Object like functionality (compareTo, String representation, etc.). Cheers, -Christopher -- 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.
