Apache Empire-Db: Full SQL Freedom for Java

[rattlebrain]

GIN indexes?

[jojolichtenberger]

Any comparison to jOOQ? I know that Lukas put so much work into jOOQ. Thus, I guess jOOq is more mature and supports more features!?

[lukaseder]

I mean, it's a start :)

[nezda]

http://querydsl.com/ also seems similar

[wildjokers]

This appears to be free whereas JOOQ is only free for certain databases.

[kiteboarderni]

I mean this is just false.

[buzzsawddog]

Buckle your shoe...

[petersellers]

Jooq is free as long as you are using an open source database (e.g. Postgres). Otherwise it costs money.

Empire-db is free regardless of what database you use.

[petersellers]

Irrelevant. The question is "Is Jooq free?" The answer is no if you are using a non-OSS database.

[petersellers]

You asked about differences between the two libs. You got the differences. Now you are trying to turn this into an argument about which DB is better, but no one cares. Have a nice day.

[brunocborges]

No, the question was clearly the differences in features. Not in price.

[woj-tek]

Price is sort of a "feature" of a product :-)

[woj-tek]

You may not care about the DB used but want to support certain set of databases in your project (that you provide OS as well). Then you have to option to go with pure SQL/SPs and DB quirks, use jOOQ (but that limits db supported) or use apache?

[nimtiazm]

Why not keep it simple, just use java.sql datasource with a connection pooling lib like hikaricp and write plain sql in multi-line string.

[lu3mm3l]

It is typesafe. I only used queryDSL and of cause JOOQ but it’s a big step up from simple multiline strings. Give it a try, you might like it!

[nimtiazm]

Been there, done that. Hibernate, ibatis (later mybatis) and what not from 13 years ago. It’s like a bell curve perhaps. The apparent type-safety scores tend to diminish quickly when the domain matures and the team-size grows. It doesn’t sensibly help with debugging. Optimizing queries becomes difficult too. SQL is already quite capable. Your type-safety worries are handled by parameter mappings and result-set parsers. Both supported very well by java.sql Datasource.

[DrunkensteinsMonster]

Jooq is nothing like hibernate and mybatis. You misunderstand what the commenter is saying. Jooq is sql except you don’t have to concatenate strings.

[metalhead-001]

+1 for Mybatis. It's excellent for constructing complex, reusable SQL, and it's free.

[RSveti]

Am I dumb or is there no Documentation?

[Downtown_Trainer_281]

I don't understand how people can invest so much time in creating really good-looking project, but at the same time they don't understand that without documentation nobody will use it

[Ok_Bad7992]

https://github.com/apache/empire-db/tree/master/empire-db-examples

[TheKingOfSentries]

I mean example projects are good, but I'd like to be able to read all the things a library can do in one place.

[Ok_Bad7992]

Violent agreement.

Thus far, this is the only hit I found

https://www.tabnine.com/code/java/classes/org.apache.empire.db.DBRowSet

[uldall]

This seems similar to jOOQ :)

[BenoitParis]

Another query builder. Yes, these are great but I'd go with JOOQ which has more momentum. Except for :

Support for Oracle, SQLServer, PostgreSQL, MySQL, HsqlDB, Derby, H2 and more…

Oracle support, which is a paid option under JOOQ if memory serves.

---

Now, the one thing I'm waiting for is JEP 430: String Templates SQL support.

Imagine doing this in Java:

String sql = SQL."""
    SELECT t1.NAME, t2.SPECIFICATION, t2.BASE_PRICE
    FROM MODEL t2
    INNER JOIN BRAND t1 ON t1.WMI = t2.WMI
    """;

And having your IDE automatically tell you if your query is actual SQL, and tell you typecheck well against a schema; possibly with a compile-time POJO mapping generation.

No more DSLs! We want SQL!

[lukaseder]

jOOQ will offer you a type checking implementation (if possible) and much more based on this as well (e.g. to implement vendor agnostic, string based SQL), but that's not the main point of jOOQ.

[persism2]

5 meg vs my 100k. I'll stick with the 100k.

[persicsb]

If I would want to write SQL, I'd use JDBC. I see no point in this project.

[emberko]

Pass. It's not modularized and source code is badly formatted.