In the SBT project class there should be a line: // Declare MySQL connector Dependency val mysql = “mysql” % “mysql-connector-java” % “5.1.12” This will import the JDBC driver JAR file for MySQL. Did you load the driver? If you use this Util class to fetch the connections, the driver will be loaded exactly one … Read more
I suspect you would want to use the DatabaseMetaData class. Most likely DatabaseMetaData.getDatabaseProductName would be sufficient, though you may also want to use the getDatabaseProductVersion method if you have code that depends on the particular version of the particular database you’re working with.
Only reasonable reason I can see is to get rid of the connection.commit() and connection.rollback() boilerplate in simple single-query transactions in small applications. JDBC in raw form requires by itself already a lot of boilerplate. Every line less makes JDBC less scary to starters.
Personally I’d use a pool as this will take care of all of the resource management for you. If your connection requirements change then you can easily modify the pool configuration. With a pool in place you can open/close connections and prepared statements according to best-practice and leave the resource management to the pool. Typically, … Read more
If your database change infrequently, you could use the data source that comes with the database’s JDBC driver and isolate the calls to the 3rd party library in a provider (My example uses the one provided by the H2 dataabse, but all JDBC providers should have one). If you change to a different implementation of … Read more
I had the same issue and it was absolutely maddening. Here’s what the docs say on the MySQL website (emphasis mine) Should the driver try to re-establish stale and/or dead connections? If enabled the driver will throw an exception for a queries issued on a stale or dead connection, which belong to the current transaction, … Read more
For Java 7 you can simply omit the Class.forName() statement as it is not really required. For Java 8 you cannot use the JDBC-ODBC Bridge because it has been removed. You will need to use something like UCanAccess instead. For more information, see Manipulating an Access database from Java without ODBC
The “14” and “6” in those driver names refer to the JVM they were written for. If you’re still using JDK 1.4 I’d say you have a serious problem and need to upgrade. JDK 1.4 is long past its useful support life. It didn’t even have generics! JDK 6 u21 is the current production standard … Read more
First, the PreparedStatement placeholders (those ? things) are for column values only, not for table names, column names, SQL functions/clauses, etcetera. Better use String#format() instead. Second, you should not quote the placeholders like ‘?’, it would only malform the final query. The PreparedStatement setters already do the quoting (and escaping) job for you. Here’s the … Read more
Immediately after your execute statement you can have an if statement. For example ResultSet rs = statement.execute(); if (!rs.next()){ //ResultSet is empty }