HackerTrans
TopNewTrendsCommentsPastAskShowJobs

lukaseder

1,268 karmajoined قبل 13 سنة
Java and databases are my professional passion. When they work together, great software can evolve. Many proprietary and standard ideas have been around to make them work together. I feel that there is yet one missing piece gluing them together more intuitively. That's why I created jOOQ:

jOOQ effectively combines complex SQL, typesafety, source code generation, active records, stored procedures, advanced data types, and Java in a fluent, intuitive DSL.

comments

lukaseder
·قبل 18 ساعة·discuss
Informix also supports MULTISET natively. Many others support ARRAY, which is equivalent for all practical purposes. jOOQ popularised MULTISET over ARRAY because the existing ARRAY support was less user friendly, mapping results to actual Java array types.
lukaseder
·قبل 18 ساعة·discuss
ISO/IEC 9075-2:2023(E) 10.9 <aggregate function>:

<array aggregate function> ::= ARRAY_AGG <left paren> <value expression> [ ORDER BY <sort specification list> ] <right paren>

I hope this helps
lukaseder
·قبل شهرين·discuss
You get that in Kotlin. Or r.getId(), r.getFirstName(), etc. in Java. So what's the issue here?
lukaseder
·قبل 9 أشهر·discuss
jOOQ is also a great option if you do like stored procedures
lukaseder
·قبل 10 أشهر·discuss
Not sure what you mean. I meant that without declaration site variance, ("pragmatic") unsafe casting is everywhere in jOOQ's internals. Without being able to capture wildcards in local type variables, ("pragmatic") rawtypes are everywhere as well (check Collections.swap() for an illustration)
lukaseder
·قبل 11 شهرًا·discuss
jOOQ's internals are full of unsafe casts, though.