The way I see it, the TableEngine interface has the potential to enable traditional SQL access to many NoSQL style stores, while removing the burden of implementing a JDBC driver (and SQL parser) and enabling the developer to concentrate on the much smaller task of the data to table adapter portion.
In my specific use case, each table would have a different path; but there may be other optional config options that are specific to the engine that could be passed in. Examples might include map fill factors, debugging options? I'm wary of YAGNI too; so if there is an alternative to my suggestion then I'm happy to look into it instead. On Thursday, May 30, 2013 2:42:23 AM UTC-4, Thomas Mueller wrote: > > Hi, > > Let's concentrate on current use cases. I wouldn't want to implement a > feature that _might_ be useful in the future (do you know the term YAGNI?). > > The path on disk, isn't it just the path of the database? Is the path > different for each table in a database? What are the other arguments you > need? What kind of table engine is it? > > Regards, > Thomas > > > On Wednesday, May 29, 2013, Andrew Franklin wrote: > >> I have written a custom TableEngine implementation that requires >> additional arguments (eg. a path on disk to the underlying file). >> >> I could possible provide some of these arguments via the session, >> however, in some cases I envisage I will have multiple tables making use of >> differently configured instances of the same TableEngine. I was thinking >> that it may be useful to add arbitrary key/value pairs to the >> CreateTableData object, passed with something like the WITH syntax in >> Postgres (http://www.postgresql.org/docs/9.1/static/sql-createtable.html >> ). >> >> If this is something that is useful to others, and the syntax is >> approved, then I can write up a patch. >> >> -- >> 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?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
