4 ms·

Just had a look at jDBI and it doesn't exactly look like a simple library to me. There's a lot of run-time annotation processing. Have a look at jOOQ if you ha

by hrjet 12y ago

Just had a look at jDBI and it doesn't exactly look like a simple library to me. There's a lot of run-time annotation processing. Have a look at jOOQ if you haven't seen it yet. There is a pre-compilation stage which generates DAO for you and they can then be used with static type guarantees.

dmacvicar 12y ago
I mentioned I haven't used it, I only got the impression from the API, but you are criticizing the implementation right, not the API?
revscat 12y ago
That pre-compilation step, though... How does that play with the IDE? I'm looking into various (more) modern ORM/DB-talky-to-things, and checked out jOOQ but was turned off by that pre-compilation step. I like having my errors bright and red when I type. I also don't like code generation. I'm not closed-minded to it, just don't like it if I can avoid it.
- hrjet 12y ago
  > That pre-compilation step, though... How does that play with the IDE? It doesn't integrate with the IDE and I am not too fond of it either. But if you want ORM as a library in Java, I don't think there is any other option possible. Java has no meta-programming support, and annotations are going to be processed at run-time which is even worse than pre-compilation.
- lukaseder 12y ago
  > but was turned off by that pre-compilation step. I like having my errors bright and red when I type. Too bad. Once you have code generation built in your development process (e.g. combining things with Flyway: http://blog.jooq.org/2014/06/25/flyway-and-jooq-for-unbeatable-sql-development-productivity/ http://blog.jooq.org/2014/06/25/flyway-and-jooq-for-unbeatab...), I'm sure you'll get a hang of how things work with jOOQ, and most importantly, you'll get your errors bright and red when you type (or when you build)
- kazagistar 12y ago
  I don't see any reason it shouldn't be possible to support pre-compilation steps as part of the IDE. Unless you are actively editing the bits that are compiled, it seems like this should work, but I am not an expert on what goes on behind the curtains of IDEs.

by hrjet 12y ago

dmacvicar 12y ago

I mentioned I haven't used it, I only got the impression from the API, but you are criticizing the implementation right, not the API?

revscat 12y ago

That pre-compilation step, though... How does that play with the IDE? I'm looking into various (more) modern ORM/DB-talky-to-things, and checked out jOOQ but was turned off by that pre-compilation step. I like having my errors bright and red when I type. I also don't like code generation. I'm not closed-minded to it, just don't like it if I can avoid it.

hrjet 12y ago
> That pre-compilation step, though... How does that play with the IDE? It doesn't integrate with the IDE and I am not too fond of it either. But if you want ORM as a library in Java, I don't think there is any other option possible. Java has no meta-programming support, and annotations are going to be processed at run-time which is even worse than pre-compilation.
lukaseder 12y ago
> but was turned off by that pre-compilation step. I like having my errors bright and red when I type. Too bad. Once you have code generation built in your development process (e.g. combining things with Flyway: http://blog.jooq.org/2014/06/25/flyway-and-jooq-for-unbeatable-sql-development-productivity/ http://blog.jooq.org/2014/06/25/flyway-and-jooq-for-unbeatab...), I'm sure you'll get a hang of how things work with jOOQ, and most importantly, you'll get your errors bright and red when you type (or when you build)
kazagistar 12y ago
I don't see any reason it shouldn't be possible to support pre-compilation steps as part of the IDE. Unless you are actively editing the bits that are compiled, it seems like this should work, but I am not an expert on what goes on behind the curtains of IDEs.