From: Shlomy R. <sre...@gm...> - 2008-04-29 19:13:29
|
> One suggestion which may make this the DB implementation easier to choose. > Why not use the SQL plugin as a dependency? This way you can let users > decide which database they want to use by setting it up in the SQL plugin, > then your plugin can use it to get connections and execute SQL etc... As > long as you stick to standard SQL there shouldn't be any problems between > the different databases. > > Then you can include any Java DB for users out of the box, but say that if > they'd like better performance they should use a different one. > Sounds like a good idea, but first ... Can the SQL plugin work with in-memory or cached tables? Is there a way to configure the underlying database? And, most importantly, do you know how much work switching to SQL plugin requires? I didn't see any documentation for coding with it. |