dzikoysk / sqiffy Goto Github PK

#5

Unfortunately, we cannot add autoIncrement(), because it leads to """id""" in queries due to the bug in exposed impl:

• Blocked by: JetBrains/Exposed#1658

Sth like:

CustomFunction fn = CustomFunction("COUNT($1)", UserTableNames.ID)

database
  .select(UserTable)
  .slice(fn)
  .groupBy(fn)
  .map { it[fn] }

Transactions between different domains should be avoided for several reasons, but if it's absolutely necessary, Sqiffy could provide relatively convinient wrapper for transaction context around Jdbi API.

Current workaround: Create dedicated data layer that combines affected domains & use raw Jdbi instance to interact with jdbc transactions.

It might be nice for string-based libs like e.g. https://jdbi.org/

Provide bindings for regular annotation processor & kapt.

SQLite is relatively bad solution for a database that will be updated in the future due to:

• Lack of quite a lot of crucial types
• Enums are not supported
• RETYPE operation would be limited to a given group of type affinities: https://www.sqlite.org/datatype3.html
• Constraints update require redeclaration of the whole table & full copy of its content
  • Currently, Sqiffy uses a workaround with a modification of table scheme stored in sqlite_master. (experimental)
• Inserts does not return autogenerated keys, so it requires additional select in the transaction to properly obtain last inserted row record

Todo:

• Provide a strict mode that forbids to use features that are not directly supported by this db
  • Enums
  • Constraint updates
  • Column type changes

If you do not specify the length of the VARCHAR data type which is details, it will currently result in varchar(null) and cause exceptions to be thrown in the console.

• User should be able to exclude fields from DTO
• Entity should contain method toDto()
• DTO should be able to implement selected interfaces

• https://github.com/MariaDB4j/MariaDB4j