lukaseder

9 ms·

91.
by lukaseder 9y ago
The biggest fallacy in this particular debate is the idea that ORMs are somewhat "higher level" whereas SQL is "lower level". SQL is a 4GL, and as such, a much more higher level language than anything you can do with a
92.
by lukaseder 9y ago
1. For static SQL, write views or procedures (i.e. raw SQL). 2. For dynamic SQL, use jOOQ or something similar in your language. 3. For the rare case of really needing object graph persistence (loading a graph of entities, manipulating it
93.
by lukaseder 9y ago
Yep. Schema-on-read (E.g. MongoDB) or schema-on-write (E.g. Oracle)
94.
by lukaseder 9y ago
https://www.tuppers-formula.tk/
95.
The informational ecosystem of net neutrality(internet-regulation.org)
1 points by lukaseder 9y ago|0 comments
96.
Finding all palindromes contained in strings with SQL(blog.jooq.org)
1 points by lukaseder 9y ago|0 comments
97.
by lukaseder 9y ago
ROWNUM is actually more tricky than an extra attribute of the table, as it is influenced by ORDER BY. I guess I wouldn't prioritise support for ROWNUM, though. There are more interesting, and more standard things. E.g. comparing a corr
98.
by lukaseder 9y ago
I'm sure bags cause some trouble, but I had something much "simpler" in mind. For instance, JOIN elimination is a powerful tool implemented by most modern RDBMS' optimisers. Take this query: SELECT c.* FROM cus
99.
by lukaseder 9y ago
Yes, I understood later on that you're not supporting union yet. Would have been nice, though, there are quite some caveats when trying to transform distinct / union into one another... :) Btw, another parser error happened when I
100.
by lukaseder 9y ago
Another question: How do you plan on handling non-deterministic expressions, such as CURRENT_TIMESTAMP or ROWNUM, et al.?
101.
by lukaseder 9y ago
Me again - I really like the idea. I wish I had something like that at a previous job, where queries ran against some 10-level nested views, involving tons of unnecessary joins, projections, unions, sorts, distincts, and what not. I'm
102.
by lukaseder 9y ago
Nice idea, but it breaks quite quickly (still). Tried to see if Cosette can prove equivalence of these two queries: /* define schema s1, here s1 can contain any number of attributes, but it has to at least contain
103.
Avoiding burnout or lessons learned from six years as an independent consultant(manuel.bernhardt.io)
1 points by lukaseder 9y ago|0 comments
104.
by lukaseder 9y ago
That's a really interesting question, and the best answer is: You have to write this manually. The SQL/JDBC/jOOQ layer can only generate system exceptions, like a constraint violation exception in this case. But there are man
105.
by lukaseder 9y ago
> There is always a schema It has a name. Schema-on-write (static schema) vs. schema-on-read (dynamic schema).
106.
Prohuddle: database related webinars (slight bias towards Oracle)(prohuddle.com)
2 points by lukaseder 10y ago|0 comments
107.
Creating tables dum and dee in PostgreSQL(blog.jooq.org)
2 points by lukaseder 10y ago|0 comments
108.
by lukaseder 10y ago
> other than sometimes poor documentation Thanks for your feedback. We're currently collecting API that is not documented well enough yet. Your feedback would be very welcome: https://github.com/jOOQ/jOOQ/i
109.
by lukaseder 10y ago
Lukas Eder here. Absolutely in favour of 1-1 SQL. In some cases jOOQ is great help, writing SQL queries with it. In other cases jOOQ is also great help accessing your stored procedures where the SQL queries are.
110.
by lukaseder 10y ago
There will always be 1-2 queries that can be proven to work better in an alternative query language, other than SQL. For instance, I can surely find a couple of awesome graph queries in the Cypher query language (Neo4j). Or some JSON querie
111.
The performance impact of SQL WITH clause on all major relational databases(modern-sql.com)
3 points by lukaseder 10y ago|0 comments
112.
by lukaseder 10y ago
Sure! Ping me if you have more questions. I'm curious to learn from your use-case.
113.
by lukaseder 10y ago
What's the difference between dual licensing and "providing some components in a private (= restriced licensed) way" ?
114.
by lukaseder 10y ago
There are different things we did (emphasis on "we". YMMV): - Check prices of other products in the same market (by market, I don't mean ORM in our case but all libraries, including UI libraries like Sencha's products, o
115.
by lukaseder 10y ago
Dual licensing is a great option. I.e. don't wait for someone to be "generous" and "pitiful". Demand money. Make it a business. Screw OSS, because after all, you're not doing it for the philosophy or Richard St
116.
A guide to the Phantom Read anomaly, and how it differs between 2PL and MVCC(vladmihalcea.com)
2 points by lukaseder 10y ago|0 comments
117.
by lukaseder 10y ago
I always link to this article: http://tapoueh.org/blog/2013/08/20-Window-Functions
118.
A comprehensive guide to the many different ways to JOIN tables in SQL(blog.jooq.org)
4 points by lukaseder 10y ago|0 comments
119.
Millions of queries per second: PostgreSQL and MySQL with demanding workloads(percona.com)
3 points by lukaseder 10y ago|0 comments
120.
by lukaseder 10y ago
Logical windowing is not available in those other databases, i.e. only Oracle can specify a window whose size depends on the content of the current row, rather than a fixed number of rows.

More ›