lukaseder

10 ms·

61.
by lukaseder 7y ago
> It was absolutely a huge use case that people would submit deeply paginated queries directly, such as from saved search result links to resume later How would offset pagination matter to these folks? They would have probably had an eve
62.
by lukaseder 7y ago
This is not at all related to RDBMS. You would still prefer keyset pagination in a "highly scalable" nosql database. Meanwhile, I'll wait for that convincing example of where "some people" want to find 3170-3179 use
63.
by lukaseder 7y ago
It is solved with keyset pagination to be precise. "I don't want to lose my place in the feed" - well, you just lost it because of OFFSET.
64.
by lukaseder 7y ago
In fact, with offset pagination, there's no way you can ever get back to that item, because you didn't reference the item, you referenced page 317. By the time you go back to page 317, there are 28 new items, and the item you ca
65.
by lukaseder 7y ago
Thanks for your nice words, I really appreciate it! :)
66.
by lukaseder 7y ago
I like that line of thoughts. Given that we have a parser, too, it's more like a 27:27 mapping: https://www.jooq.org/translate
67.
by lukaseder 7y ago
I've had people tell me they learned a ton about SQL constructs they were unaware of because they just discovered about them by auto completing on the jOOQ API. If you know SQL, you won't spend much time looking up how the jOOQ AP
68.
Java Database Access: An Overview Guide(marcobehler.com)
2 points by lukaseder 7y ago|0 comments
69.
by lukaseder 7y ago
We also have a solution: https://www.jooq.org/translate/
70.
by lukaseder 7y ago
> I have noticed that many authors of SQL articles don't seem to be aware of Oracles quirks I've spent much more time with Oracle than with other RDBMS. So, what made you think so? > The author didn't specify any partic
71.
by lukaseder 7y ago
Oracle's (+) syntax does not allow for full outer joins. The conclusion would be the same with Oracle's syntax. It's just more obscure, as it would turn into a "fa.film_id < 10" vs "fa.film_id(+) < 10&qu
72.
by lukaseder 8y ago
"Funny guy" here. Can't comment on db zealots. It must suck when that happens. But disagree entirely on your other parts. Haven't run into such cases yet, wrote all my reports in SQL (and something like XSLT for presenta
73.
by lukaseder 8y ago
Very cool (and how could I miss it?)
74.
by lukaseder 8y ago
What's your library?
75.
by lukaseder 8y ago
jOOQ!
76.
by lukaseder 8y ago
Yes that's what this talk is about. A lot of people recognise apples and oranges for what they are. The talk is meaningless to those people. A lot of other people don't / can't make the distinction (yet). For those peo
77.
by lukaseder 8y ago
I know you didn't attack me, just wanted to make sure the pendulum won't swing too far to the opposite side :)
78.
by lukaseder 8y ago
I like this analogy given that the relational model solved all the problems of networked/hierarchical models, which preceded it. Yet, NoSQL aimed to regress towards pre-SQL times
79.
by lukaseder 8y ago
Presenter here. Yes that's pretty much it. There are many more convincing reasons than window functions in the second part which focuses on the execution of a 4GL, not the development with it. Just to be clear: the talk uses hyperbolic
80.
by lukaseder 8y ago
ORMs like Hibernate / jOOQ work around this by providing a convenient "dot notation" to navigate a foreign key path. This is particularly useful when keys are composite. See for example: https://blog.jooq.org/
81.
by lukaseder 8y ago
I mean this: https://fivethirtyeight.datasettes.com/fivethirtyeight-c9e67...
82.
by lukaseder 8y ago
> On security: the data is read-only, using SQLite’s immutable mode. You can’t damage it with a query—INSERT and UPDATEs will simply throw harmless errors. In times of data breaches, the naivety of this statement is alarming. It is not t
83.
PostgreSQL 11 support for SQL standard GROUPS and EXCLUDE window function clause(blog.jooq.org)
2 points by lukaseder 8y ago|0 comments
84.
by lukaseder 8y ago
The point of jOOQ is for developers to write SQL (almost) exactly as if Java natively supported the SQL language. Not hide SQL behind some "more idiomatic" collection API. So, jOOQ will never become quill or end up looking like it
85.
by lukaseder 8y ago
No
86.
by lukaseder 8y ago
1. Why not just use the Stream API? 2. JINQ (as a name) already exists: http://www.jinq.org
87.
by lukaseder 8y ago
> Just keep making jOOQ a great to use library. :) Will do! Thanks for the nice words about the blog.
88.
by lukaseder 8y ago
Hey Mat, thanks for spreading the love. Hope you never stop using RDBMS! Fancy a couple of jOOQ stickers? :)
89.
by lukaseder 8y ago
> “compared to other popular ORM frameworks such as Django and Hibernate, Rails has 2x more applications on GitHub with 400 or more stars than Django and Hibernate combined.” As if the whole world was hosted on GitHub...
90.
by lukaseder 8y ago
Definitely no one runs jOOQ's code generation from the production database. Apart from the security concerns you've mentioned, that wouldn't make any sense, technically. When you implement a database increment, you will want

More ›