In stepping back, I can see how people might easily get confused based on the history of the JDBC driver. In my investigations of this, I have found that this is almost always due to confusion over the classname to use to register the JDBC driver, and the URL’s to use to actually connect to the database. I have heard from customers that connecting to SQL Anywhereover JDBC can be difficult at times. I am reposting it here with a few minor updates, since I still refer to it occasionally and I think it is still useful.
I originally posted this a few years ago to help people configure their Java applications to use the iAnywhere JDBC driver, which was replaced by the SQL Anywhere JDBC driver in SQL Anywhere version 12.
0 kommentar(er)
