Hi, Just my 2 cents.
I'm pro for the customisable file extension, but I don't think there should be allowed custom data before and after the header. I don't think anything should write to the database file except for H2 itself, even if just for reliability. If you want to store extra data as configuration or anything else, then it can be stored in a H2 table.
Also, I was thinking with having data after the file header or before, if you change the length of data before it will need to shift the entire database file along and every time h2 changes the length of the database file it will need to copy the data after the ender. So it would be a huge performance hit as the database grows in size. It would be much better off the data being stored in a h2 table and h2 managing it.
Anyway, just my thoughts. Cheers, Ryan -- 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.
