Thomas I know the roadmap and I agree with this priorities , but if there are a way to create a table with a column of type null and then even H2 can't use that table ... Nothing abstract, many of us just know that and work-around that needlessly , but the worst part is about SQL portability. A working and syntactically correct SQL on H2, MySql, PgSql, DB2, etc. has a different result only in H2 !
Use case driven plan it's fine, but remember the difference between fish and fishing rod ;-) regards, Dario > What I mean is: what is your concrete, real use case? For example: I > write an application to do X and need this feature because of Y. Or: I > use Hibernate, and Hibernate generated this code,... or something > similar. > > Reason: I usually prioritize real world use cases higher than > theoretical (abstract) ones. > -- 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.
