4 ms·
How does it handle operations more complex than "select * from user"? For example, joins and subqueries. And wouldn't it be nicer to have the database layer f
by revetkn 13y ago
How does it handle operations more complex than "select * from user"? For example, joins and subqueries. And wouldn't it be nicer to have the database layer figure out properties for you instead of writing mapping code by hand?
For example (this uses SQL, I am not big on ORMs):
User user = database.queryForObject("SELECT * FROM user WHERE user_id=?", User.class, userId);
- lukaseder 13y agoThis boils down to whether you prefer SQL to be an external or internal DSL in your host environment. External DSL = Actual target language, no simulation thereof, but String-based, no typesafety, detached bind variables, SQL injection, etc. Internal DSL = Typesafe, compiled, but only a simulation of the real language, limited by the host language
- revetkn 13y agoBTW, I just checked out jOOQ. I think you did a great job with it. This is the first ORM I've seen that really embraces SQL. Nice work
- lukaseder 13y agoThanks. And it will stay that way. Unlike many competitor products, there are no plans to support / unify any NoSQL, LDAP, or other data stores. If they don't implement the SQL language first, they won't be integrated.