metio/yosql

zero dependency database access for java

YoSQL

Take a look at the project website to read the documentation.

License

To the extent possible under law, the author(s) have dedicated all copyright
and related and neighboring rights to this software to the public domain
worldwide. This software is distributed without any warranty.

You should have received a copy of the CC0 Public Domain Dedication along with
this software. If not, see https://creativecommons.org/publicdomain/zero/1.0/.

yosql's Issues

Support Spring/CDI/Guice/DI

DataSource + Converters could be injected into the constructor of a repository.

allow to pass in set of files

sign waiver

requires #34

Configure directory layout

Instead of creating folders w/ SQL files in them, users might want to define a single SQL file that contains multiple statements to declare which repositories should be generated.

add to openhub.net

change from local- to remote-repository for bazel-build-process

blocked by sebhoss/bazel-build-process#1

Support returning SQL statements

SQL allows us to write something like INSERT INTO ... RETURNING which returns what we just wrote into the database.

reduce number of repos per sample

Runtime is too high otherwise since more and more usecase are being added

remove empty root BUILD

Allow to overwrite error/log messages

The code generator could read a .properties file to load translations and use them in the generated code.

enable continuous deployment

add file headers

reference LICENSE in the root

mark build goal as phony

Add jooq based API

Instead of using the raw JDBC API, we could use jooq to execute the SQL statements.

Integrate w/ Apache Camel

We could generate the necessary glue code to convert a repository into a Camel producer/consumer

re-enable yosql-maven-plugin

blocked by dagger2 migration

Convert Parameters

Converting parameters before handing them over to the JDBC API should be supported out of convenience for users. Instead of converting the parameters before calling the repository, the repository could do the conversion itself

open up mirrors

• gitlab
• bitbucket
• pika
• repo.or.cz

rename benchmarks to yosql-benchmarks

Add foldable comment code blocks

In order to make the generated code easier to read, code blocks could be defined in comments. IntelliJ users could collapse these blocks - Eclipse does not support it (yet)

add makefile

add contributor guide

Allow to load SQL statements at runtime

Instead of inlining them into the generated code, we could load them from file at runtime. This might make it easier for dynamic environments like OSGi to change to statement after deployment without releasing a new version of the generated repositories.

repositorySqlStatements currently only support "inline"

Consider lesser known JDBC API alternatives

Take a look at:

• https://github.com/zsoltherpai/fluent-jdbc
• https://github.com/bendem/sql-streams
• https://github.com/jtouzy/fastrecord
• https://github.com/pyranid/pyranid
• https://github.com/mjdbc/mjdbc
• http://jdbi.org/
• https://github.com/brettwooldridge/SansOrm

merge package level BUILD files

Add spring-jdbc based API

Use JdbcTemplate & NamedParameterJdbcTemplate instead of the raw JDBC API

create project website

Create/use subelements to configure plugin

Instead of prefixing configuration names with method, we could introduce a MethodConfig type that contains all these config options.

update parameter documentation

Generate interfaces for repositories

Interfaces might be useful for testing & mocking. Besides the interface name & location, the implementation package for the repository should be configurable.

Support unnamed parameters

Unnamed parameters (?) should be supported as well. Yesql exposes an extra varargs argument to the generated repositories which are getting applied in order

Write performance test for framework-comparison

See https://github.com/bwajtr/java-persistence-frameworks-comparison

add license badge to readme

implement gradle plugin

Should have the same features/configuration as the maven plugin

Use simpleflatmapper to map between results & beans

To make it easier for users to get their own types back from the database, we could support things like Use http://simpleflatmapper.org/ to automatically convert to the wanted type.

add benchmark goals to makefile

support TI

https://github.com/sebhoss/thats-interesting.java

migrate to dagger2

Can't use Plexus API in Gradle plugins, nor in CLI. Dagger2 offers nice speed and can be used everywhere

setup CI/CD

blocked by Bazel install on build.metio.wtf: metio/build.metio.wtf#1

Support symbols in query names (& .sql files)

Yessql supports special symbols like ! to indicate that a SQL statements writes, or < to indicate that a SQL statement returns

add CoC

add openhub badge to readme

remove pom.xml

add coverage make goal

Verify that SQL statement name aligns w/ Java naming rules

Right now, the name is taken verbatim without any checks or modifications. If we already know that a name is invalid (according to Java rules), the plugin should throw an error.

rename testutils into yosql-testutils

Support generics

Generics should work for both input parameters and return types

add waiver

re-enable examples w/ bazel

Add CLI

A CLI would be useful for bazel based builds