Hi, The historic extension for a data file containing an unspecified (or non standard) data format is: .DAT or .BIN
For many admin reasons I like the way several well known databases use to organize storage in a very predictable directory hierarchy. I think it's much better that storage of a database that involve more than a single file should be a directory with a name that contain a prefix/suffix that express the vendor and the database name. Like: /h2db-databaname/ ... or: /h2dbdir/databasename/ ... Inside database data directory any file it's considered belonging to database and files extensions become less relevant. Anyway .h2db is very expressive as extension. Or .h2.dat , .h2.log , .h2.trace , etc. The main benefit of these conventions is to facilitate searches in the file system, to express the file type, database and dbm vendor to which they belong. I know that next words are out of scope in this thread - but it's related to. A usefull concept to organize physical database storage it's the TABLESPACE database object , that specify an storage URI and type. This concept support partitioning and physical organization, where any database has a default TABLESPACE in witch all tables are stored, except that they specify a tablespace at creation time. This make possible the use of different tablespaces (RO/RW , Fast/Slow , Local/Remote) for different tables and indexes on the same database. regards, Dario El 08/05/10 02:33, Thomas Mueller escribió: > I understand. I think by default databases should have a suffix > (currently it's .h2.db). I understand in some cases this should be a > different suffix. What about an escape mechanism? For example, if the > database ends with a slash, then the regular suffix is not used. > Examples: > > jdbc:h2:~/data (will create a file named "data.h2.db") > jdbc:h2:~/data.db/ (will create a file named "data.db") > jdbc:h2:~/data/ (will create a file named "data") > > Other ideas are welcome. > > Currently the default suffix is ".h2.db". It would be better if the > suffix has only one dot by default. What about .h2db? I will add a > feature request. However, for backward compatibility, I don't plan to > change it in the near future. > > So I will add two feature requests: > > - Database file name suffix: a way to use no or a different suffix > (for example using a slash). > - Database file name suffix: should only have one dot by default. Example: > .h2db > -- 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.
