Slightly worried that only 8 LiveJournal users have JDBC listed as an interest, when 62 are interested in chairs!
dplass is the only name I recognise from those eight...
I have some Java freeware that I distribute using Java Web Start. For the sake of learning SQL and JDBC I want to add a feature so that statistics generated by my software can optionally be added to a SQL database.
What aspects of the SQL stuff have to be configurable?
Currently I'm using the JDBC/ODBC bridge to reach MySQL. I am aware of com.mysql.jdbc.Driver but am keeping things simple until I know what I am doing.
What if the customer has a better driver (with a different URL format) they want to use or a different DBMS (is there a better one that I could hardcode? Do I then have to ship the Java classes? Or point to them in my Java Web Start .jnlp file? My product is closed-source if it matters).
My target audience will already have an SQL database but will not have any Java expertise: it must be a one-click installation from Java Web Start followed by filling in a form to say how to connect to the database.
