SQLiteJDBC
SQLiteJDBC is a Java JDBC driver for SQLite 3. It comes as either a pure Java driver based on NestedVM or a native JNI library. Native binaries are provided for Mac OS X and Windows.
| Tags | Database API Software Development Libraries |
|---|---|
| Licenses | BSD Revised |
| Operating Systems | Mac OS X Windows Windows POSIX BSD Linux |
| Implementation | Java |
Recent releases
- 06 Dec 2008 21:55
Changes: The code was updated for SQLite 3.6.3. The constraints on setMaxRows() were relaxed.
- 14 Aug 2008 23:15
Changes: This release has been upgraded to SQLite 3.6.1, and a Linux/AMD-64 binary has been added to the combined jar.
- 27 Jun 2008 22:57
Changes: Closing a closed statement now has no effect, and there are other bugfixes. Binary size has shrunk, and whether the amalgamated jar is running in pure or native mode can be determined by DatabaseMetaData.getDriverVersion().
- 19 Jun 2008 09:20
Changes: The native Linux binary was fixed.
- 17 Jun 2008 13:25
Changes: The driver has been repackaged with the binaries and a pure Java driver is provided in the same jar file. Use of the library path is no longer necessary.
- All comments
Recent commentsis it possible to load sqlite extension? (based on platform, e.g. .so or .dll)?
Thank you,
Francesco
I'd like to compile the JNI bindings for 64-bit OS X so the sqlite-jdbc drive can be used in native mode from Java 6 on OS X (which is 64-bit only). If anyone would be willing to help me, that would be great.
First off, thanks for this great tool...I too am a mathematics major graduating this semester! Does this driver support running SQLite's dot commands like, '.output', '.mode' etc?
There appears to be a problem with wasNull() after getObject() has been called. I submitted a ticket about this, but I'm not sure if that is the right way to submit a bug.
In particular, the implementation of getObject() in the RS class calls the checkCol() method, while all other get*() methods call the markCol() method. Only the markCol() method properly updates the lastCol instance variable, which in turn is used by the wasNull() method.
This is making Hibernate fail with enum fields that are NULL.
This + Hibernate + SQLite = the easiest data store you'll ever need for a webapp. Thank you!
A couple of gotchas: doesn't handle Timestamp.class very well (workaround: store timestamps in unix "secs. since epoch" format, then write a special Hibernate UserType to convert back and forth). Also, you must be VERY specific with your connection path (jdbc:sqlite:[database.db]), otherwise you'll see empty databases with no tables. The problem is that the default behavior of SQLite is to create a *new* database when it doesn't find the database file. Which means if you specify the wrong connection path, it just happily gives you a new, blank database instead of an exception. If you're running, say, SquirrelSQL from C:\Program Files\squirrelsql, you have to use relative paths and "walk" up the file tree, then back down again to the directory of your database file. For instance: jdbc:sqlite:..\..\db\database.db.