Hello Lukas, On Wednesday, August 15, 2012 1:12:01 PM UTC+7, Lukas Eder wrote: > > > As i understand it, firebird doesn't have a "schema" in this sense > either. > Are you sure? > > http://www.firebirdsql.org/file/documentation/reference_manuals/reference_material/html/langrefupd25-ddl-database.html > > Yes. http://www.firebirdfaq.org/faq232/
> Nice links. The FAQ's indicate that there are some SHOW TABLES, SHOW > TABLE commands. That might be easier to use than querying the actual > RDB$ tables, if those commands are available through JDBC... > Ah, probably not. Those are ISQL-specific commands. http://www.firebirdfaq.org/faq231/ On the other hand, the link you gave me earlier (from alberton.info) have most of what we need, i think. > Just in case: jOOQ shouldn't rely on JDBC driver implementations. If > it's not available through the standard JDBC API, then it shouldn't be > used. > Understood. > That's just a silly convention of mine when the public API is in fact > implemented using a "final" keyword, delegating some implementation > parts to a similar method. Instead of writing ... > OK. Thank you for clearing that up. I'm wondering about the following implementation though: ... public Factory create() { return new SQLiteFactory(getConnection()); } ... The method creates a new factory every time it's called, (instead of reusing a singleton, for example) which strikes me as a bit odd. Is this by design or am i missing something here? Currently I have a skeleton "monkey-see-monkey-do" implementation based on the SQLiteDatabase source code. I'm not sure how to actually test this though. Please let me know how i can send you the files if you want to take a look. Regards, ts.
