This is a fork to specifically support CEROD, a C Extention for SQLite3. SQLite JDBC Driver compatibility is 100% maintained to allow for effortless synch with the original upstream (SQLite JDBC Driver) project !!
[Learn more about the SQLITE-JDBC CEROD Fork ](/README_CEROD.md)
Follow directions for CEROD build as described in Preparing CEROD build (README_CEROD.md)
The rest is the original README from SQLite JDBC Driver.
Note: updated 9/1/2024 as of sqlite-jdbc 3.46.1.1-SNAPSHOT
SQLite JDBC is a library for accessing and creating SQLite database files in Java.
Our SQLiteJDBC library requires no configuration since native libraries for major OSs, including Windows, macOS, Linux etc., are assembled into a single JAR (Java Archive) file.
The project is maintained, but is not being actively developed:
-
We follow every new version of SQLite and will release a corresponding version of our driver.
-
Bugs will be investigated, and fixed if possible.
-
New features are driven by pull requests.
The current maintainer of the project is gotson.
➡️ More usage examples and configuration are available in USAGE.md
SQLite JDBC is a library for accessing SQLite databases through the JDBC API. For the general usage of JDBC, see JDBC Tutorial or Oracle JDBC Documentation.
Assuming sqlite-jdbc-3.46.1.0.jar is placed in the current directory.
> javac Sample.java
> java -classpath ".;sqlite-jdbc-3.46.1.0.jar" Sample # in Windows
or
> java -classpath ".:sqlite-jdbc-3.46.1.0.jar" Sample # in macOS or Linux
name = leo
id = 1
name = yui
id = 2 import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
public class Sample
{
public static void main(String[] args)
{
// NOTE: Connection and Statement are AutoCloseable.
// Don't forget to close them both in order to avoid leaks.
try
(
// create a database connection
Connection connection = DriverManager.getConnection("jdbc:sqlite:sample.db");
Statement statement = connection.createStatement();
)
{
statement.setQueryTimeout(30); // set timeout to 30 sec.
statement.executeUpdate("drop table if exists person");
statement.executeUpdate("create table person (id integer, name string)");
statement.executeUpdate("insert into person values(1, 'leo')");
statement.executeUpdate("insert into person values(2, 'yui')");
ResultSet rs = statement.executeQuery("select * from person");
while(rs.next())
{
// read the result set
System.out.println("name = " + rs.getString("name"));
System.out.println("id = " + rs.getInt("id"));
}
}
catch(SQLException e)
{
// if the error message is "out of memory",
// it probably means no database file is found
e.printStackTrace(System.err);
}
}
}Our SQLite JDBC driver package (i.e., sqlite-jdbc-3.46.1.0.jar) contains three
types of native SQLite libraries (sqlitejdbc.dll, sqlitejdbc.dylib, sqlitejdbc.so),
each of them is compiled for Windows, macOS and Linux. An appropriate native library
file is automatically extracted into your OS’s temporary folder, when your program
loads org.sqlite.JDBC driver.
Since sqlite-jdbc-3.6.19, the natively compiled SQLite engines will be used for the following operating systems:
| x86 | x86_64 | armv5 | armv6 | armv7 | arm64 | ppc64 | riscv64 | |
|---|---|---|---|---|---|---|---|---|
Windows |
✔ |
✔ |
✔ |
✔ |
||||
macOS |
✔ |
✔ |
||||||
Linux (libc) |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
Linux (musl) |
✔ |
✔ |
✔ |
|||||
Android (API Level 24+) |
✔ |
✔ |
✔ |
✔ |
||||
FreeBSD |
✔ |
✔ |
✔ |
In the other OSs not listed above, the pure-java SQLite is used. (Applies to versions before 3.7.15)
If you want to use the native library for your OS, build the source from scratch.
Sqlite JDBC supports GraalVM native-image out of the box starting from version 3.40.1.0. There has been rudimentary support for some versions before that, but this was not actively tested by the CI.
By default, the sqlitejdbc library for the compilation target will be included in the native image, accompanied by the required JNI configuration.
At runtime, this library will be extracted to the temp folder and loaded from there.
For faster startup however, it is recommended to set the org.sqlite.lib.exportPath property at build-time.
This will export the sqlitejdbc library at build-time to the specified directory, and the library will not be included as a resource.
As a result, the native image itself will be slightly smaller and the overhead of exporting the library at run-time is eliminated,
but you need to make sure the library can be found at run-time.
The best way to do this is to simply place the library next to the executable.
This example uses the native-build-tools maven plugin:
<plugin>
<groupId>org.graalvm.buildtools</groupId>
<artifactId>native-maven-plugin</artifactId>
<configuration>
<buildArgs>
<buildArg>-Dorg.sqlite.lib.exportPath=${project.build.directory}</buildArg>
</buildArgs>
</configuration>
</plugin>This will automatically place the sqlitejdbc library in the /target folder of your project, creating a functional execution environment.
When packaging the resulting app, simply include the library in the distribution bundle.
Download from Maven Central or from the releases page.
<dependencies>
<dependency>
<groupId>org.xerial</groupId>
<artifactId>sqlite-jdbc</artifactId>
<version>3.46.1.0</version>
</dependency>
</dependencies>Snapshots of the development version are available in Sonatype’s snapshots repository.
Maven Central resources are signed using GPG and the signature files, ending in .asc, are available in the same location as the other downloads.
The following key is currently used to sign releases:
-----BEGIN PGP PUBLIC KEY BLOCK----- Comment: C1CB A75E C9BD 0BAF 8061 9354 59E0 5CE6 1818 7ED4 Comment: Taro L. Saito (For GitHub Actions) <[email protected]> xjMEYuRVGhYJKwYBBAHaRw8BAQdA2Dp4m1Yhtb1g94pQzzL24FuP6b9KXF8lP9Dh hZnynhfNM1Rhcm8gTC4gU2FpdG8gKEZvciBHaXRIdWIgQWN0aW9ucykgPGxlb0B4 ZXJpYWwub3JnPsKUBBMWCgA8FiEEwcunXsm9C6+AYZNUWeBc5hgYftQFAmLkVRoC GwMFCwkIBwIDIgIBBhUKCQgLAgQWAgMBAh4HAheAAAoJEFngXOYYGH7UfPwBAK7x TVRebZeWcAwmGaMUsbg7SgJou8xnkhByObPLUC/4AQDPsZeYmi4KXyXPzmqhCicd Y+ZSJWIDQqitK2ujPDFXA844BGLkVRoSCisGAQQBl1UBBQEBB0Atu9kejBi+6wfO T0a9z/LYEEdNXM/VX6xt1onKToPPdQMBCAfCeAQYFgoAIBYhBMHLp17JvQuvgGGT VFngXOYYGH7UBQJi5FUaAhsMAAoJEFngXOYYGH7UlMABAKyRCazhVyUFg5FOpAnm ckBY38CaMGPPLXVyY8Kr6dYFAP9wYLu7nsDZCOXkAgS+et4Pk1WZCggoYUkxsX1o 0KZXBQ== =Wyas -----END PGP PUBLIC KEY BLOCK-----
The project’s version follows the version of the SQLite library that is bundled in the jar, with an extra digit to denote the project’s increment.
For example, if the SQLite version is 3.39.2, the project version will be 3.39.2.x, where x starts at 0, and increments with every release that is not changing the SQLite version.
If the SQLite version is updated to 3.40.0, the project version will be updated to 3.40.0.0.
You may need to add shade plugin transformer to solve No suitable driver found for jdbc:sqlite: issue.
<transformer
implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
<resource>META-INF/services/java.sql.Driver</resource>
</transformer><dependency>
<groupId>org.xerial</groupId>
<artifactId>sqlite-jdbc</artifactId>
<version>3.46.1.0</version>
</dependency>We are always looking for:
-
Reviewers for issues or PRs, you can check
-
Contributors to submit PRs, you can check
and
Please read our contribution guide.