Dear Jukka, Peter, and Glen --
Happy Holidays !!!
Hope the season finds all of you well and happy.
iJSQL update:
I have the architecture divided: currently there's the core class,
iJSQL.java, and a console view class, iJSQL_Console.java. Jukka's
switchable connections are working, and I have tested it with InstantDB and
MS Access (using the jdbcodbc bridge). I'm javadoccing the code now, and
will try to sort out cvs to get it checked in. I've gone ahead and attached
the code as a zip archive, if you want to take a look. As I said, it's not
commented much yet ...
I've implemented the packaging I proposed, working Jukka's plugins into the
core tree:
com.curiousmuse.ijsql.core
com.curiousmuse.ijsql.core.plugin
com.curiousmuse.ijsql.core.pluginsamples
com.curiousmuse.ijsql.view
com.curiousmuse.ijsql.view.console
com.curiousmuse.ijsql.view.gui
I also added a LOAD option to the core iJSQL class: if the statement is in
the format "LOAD <driver classname>", the specified driver is loaded. Also,
if you specify "LOAD <driver classname> <connection string> [<username>]
[<password>]", the driver is loaded, then a connection is established to the
specified db/user/password. This connection then becomes the current
connection.
Right now, no drivers are loaded when you start an app. You must use the
LOAD command from the commandline. Here's my idea on how to handle this: we
supply a sample properties file with some common drivers specified. The
user can edit these to get the initial setup configured (for the gui view,
maybe there's a nice Swing interface to do this). The app attempts to load
these on startup. Any drivers that are LOADed by the user are added to the
properties file, or replace the current entries.
Any input on what I've done is welcome. One area I'd like feedback on is
the treatment of the member variables in the core iJSQLclass. It's not a
"pure" OO approach ... what do you think??
Best Regards,
Bill Graham
|
