Skip to content

A java sql script framework to outsource sql script from your java files

License

Notifications You must be signed in to change notification settings

lynxplay/idonis

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

32 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

idonis

Build

A really small SQL script caching framework to store complex SQL statements outside of java code.

Install

As of right now, idonis was not accepted onto maven central and therefore you will have to manually install the project into your local maven repository. You can install the project using:

curl -sL https://raw.githubusercontent.com/lynxplay/idonis/master/scripts/downloadLatest.sh | bash

Usage

After adding idonis to your dependencies using:

<dependencies>
    <dependency>
        <groupId>me.lynxplay</groupId>
        <artifactId>idonis</artifactId>
        <version>1.0-SNAPSHOT</version>
    </dependency>
</dependencies>

you can now access the entry point using the java.util.ServiceLoader. Note that this dependency will contain the actual implementation as it has to be provided in the runtime. If you have multiple projects using idonis, it is suggested to provide the idonis jar to the runtime manually and only depend on a provided idonis-api.

You can request the IdonisContainer using:

class Showcase {
    public static void main(String[] args){
        Idonis i = ServiceLoader.load(Idonis.class).findFirst().orElseThrow();
        IdonisContainer c = i.forDialect(Path.of("your" , "resource" , "path") , SQLDialect.SQLITE);
    }
}

Using this container, you can now easily request a query stored in it using:

IdonisContainer container = ...
try(PreparedStatement s = container.using("mySqlScript.sql").prepare(mySqlConnection)) {
    s.setString(1 , "name");
    ...
} catch(SQLException e) {
    ...
}

Templates

As SQL scripts may not preserve placeholder order between languages, idonis also provides a simple way to abstract templates as well. When defining an SQL script, you should replace all ? templates with idonis variables. For example, this UPSERT SQLite3 script:

/*
@id
@first_name
@last_name
*/
INSERT INTO table (id, first_name, last_name)
    VALUES (@id, @first_name, @last_name)
    ON CONFLICT(id) DO UPDATE SET first_name=@first_name,
                                  last_name=@last_name;

This template will be parsed into a known PreparedStatement instance with updated indices. As an example, this specific script could be filled like this:

IdonisContainer container = ...
try(PreparedStatement s = container.using("upsertHuman.sql").prepare(mySqlConnection)) {
    s.setInt(1 , id);
    s.setString(2, firstName);
    s.setString(3, lastName);
    ...
} catch(SQLException e) {
    ...
}

This would replace all @id occurrences with the java variable id and so one and so forth. Note that the index of a variable is simply the position of it in the comment above the actual SQL script. If the script for some reason still has ? wildcards, they will be assigned indices after the variables. Adding a ? to the SQLite3 UPSERT example would result in it being addressable on index 4.

About

A java sql script framework to outsource sql script from your java files

Resources

License

Stars

Watchers

Forks

Packages