> Yes. That's a good idea. My idea was, if the files are small, then the
duplication wouldn't be such a big problem. How large are the files in
general?
It can also be related to data management. Those files size are from
hundreds of kilobytes to hundred of megabytes, but some applications are
limited to 2GB DBF and Shp files.
> Is it important to ensure data is not corrupted on a crash ("kill -9")
or power failure? If yes, what is the plan to ensure it? If you don't have
plans yet, I'm sure we come up with a good idea (for example "overlay" the
file, that is, just store the deltas). If not, why isn't it a problem?
GeoSpatial data are less important than financial data, then corruption are
less critical. "overlay" is a good idea yes, It should be good to find a
generic interface that file drivers must implements. It is somewhat complex
to implements TableEngine each time. There is a lot of GIS file formats
http://en.wikipedia.org/wiki/GIS_file_formats .
Regards,
-Nicolas Fortin
Atelier SIG
IRSTV FR CNRS 2488
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.
