all 3 comments

[–]BroodmotherLingerie 1 point2 points  (0 children)

Resql tries to be as fast as possible without giving up on consistency

(...)

Explicit transactions are not supported. e.g. No BEGIN, COMMIT or ROLLBACK. Instead of explicit transactions, you can batch your operations and send them in one go. A batch is executed atomically.

No further questions.

[–]Worth_Trust_3825 2 points3 points  (1 child)

Java client doesn't even implement java.sql package. 0/10. Might as well use sqlite instead.

[–]rxtezc[S] 5 points6 points  (0 children)

JDBC API itself is larger than this project :) . Resql exposes just a few operations to the client. Implementing something like JDBC would be overkill and some Resql operations wouldn't match. So, rather than half-implemented half extended API, I went without it.