This is probably a bit of stretch, but I was wondering if there was any appetite for restructuring h2 so it works better as a relational db library.
That is to say something like this. Ideally the code would exist in separate folders (or even better separate sub modules, which compile independently). The type system (and the database meta) would have to become somehow plugable and not hardcoded as it is currently. h2 sql/tools/types -> h2 rdbms -> mvstore This would be a big improvement in my opinion. The sql aspect whilst important to a lot of people also represents a lot of complexity. I will probably go down this route for my own purposes, but assuming the split could be done well, would the project want to incorporate such changes? regards, Mike -- 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 h2-database+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/h2-database/CAOZwqwn-rYSZ0WznRq4f8VXkeW_6EVtWb-C%2Bvjef%2BJ-qBktBEQ%40mail.gmail.com.
