MarkusWinand

14 ms·

91.
by MarkusWinand 8y ago
> It was a bit depressing to see the solid column of Xs by SQLite Except WITH [RECURSIVE] which is in SQLite since early 2014. Damn, I forgot to use that trivia in my MySQL bashing... ;) Other than that, I met Richard Hipp in person some
92.
by MarkusWinand 8y ago
A big red X doesn't mean the database doesn't have other, similar but proprietary functionality. It just means: it doesn't support this function in a standard confirming way yet. There is nothing against using non-standard fu
93.
by MarkusWinand 8y ago
The purpose of the example is to demonstrate functional dependencies based on grouped tables.
94.
by MarkusWinand 8y ago
Those gory details I've mentioned in the article. This is how standard SQL JSON_OBJECTAGG works: https://modern-sql.com/blog/2017-06/whats-new-in-sql-2016#js... It can actually do much more: <JSON object a
95.
by MarkusWinand 8y ago
https://www.postgresql.org/search/?q=json_objectagg But there is a patch pending for this. Not sure if this gonna be included in 11.
96.
by MarkusWinand 8y ago
Hi! The first feature matrix you see is about checking of functional dependencies. For example, PostgreSQL doesn't see the functional dependency between the columns ID and MA in the result of this query. SELECT id , max(
97.
MySQL 8.0 is released (GA) bringing window functions and CTEs(dev.mysql.com)
2 points by MarkusWinand 8y ago|0 comments
98.
by MarkusWinand 9y ago
The example still groups by YEAR. So you won't need more than 12 months. Regardless: SQL is a statically typed language. Also the type of the result—i.e. the names and types of the columns—must be known in advance. Some databases offer
99.
by MarkusWinand 9y ago
Welcome :)
100.
by MarkusWinand 9y ago
I'm sorry it is not so obvious: there is a difference between red, which means it doesn't work, and transparent, which means I didn't test any further back.
101.
Standard SQL features where PostgreSQL beats its competitors(slideshare.net)
96 points by MarkusWinand 9y ago|16 comments
102.
by MarkusWinand 9y ago
It is absolutely possible. On the other hand: it's also possible that nobody would know me without the website. Further: I've learned so much from free online resources, why not giving something back? I know for sure that many peo
103.
by MarkusWinand 9y ago
I'm selling it as book. But more importantly: the "fame" sells other services. Look here: https://winand.at/
104.
by MarkusWinand 9y ago
This is a controversy outside of SQL. SQL is pretty clear what null is: > “Every [SQL] data type includes a special value, called the null value,”[0] “that is used to indicate the absence of any data value”[1] ( http://modern-s
105.
by MarkusWinand 9y ago
*Edit: exceptions :)
106.
by MarkusWinand 9y ago
Just my 2c from SQL standards perspective: > “Every [SQL] data type includes a special value, called the null value,” “that is used to indicate the absence of any data value”. ( http://modern-sql.com/concept/null ) Fo
107.
by MarkusWinand 9y ago
Yes, because it is a null reference . SQL's null is a value . The difference is that processing null values does not cause exceptions in SQL.
108.
by MarkusWinand 9y ago
I'd say this is a generally misleading statement, but if you like it is right in some context. In particular, one could argue that it is true for clustered indexes (e.g. in SQL Server or MySQL/InnoDB). In that case the table is ac
109.
The PostgreSQL Query Cost Model(shiroyasha.io)
1 points by MarkusWinand 9y ago|0 comments
110.
by MarkusWinand 9y ago
In that case, everything below 5/5 would be very bad ;)
111.
by MarkusWinand 9y ago
Not's not just outdated, its wrong (in context of question 2) which is about indexing both, `where` and `order by` clauses. In that case you must provide a single index to benefit from the index order (so that the database doesn't
112.
The 3-minute SQL indexing quiz: Can you spot the five most common mistakes?(use-the-index-luke.com)
108 points by MarkusWinand 9y ago|32 comments
113.
Free guide to SQL performance for developers now available in five languages(use-the-index-luke.com)
3 points by MarkusWinand 9y ago|0 comments
114.
Big news in databases: SQL on the rise, cloud wars, IBM in free fall(use-the-index-luke.com)
3 points by MarkusWinand 9y ago|0 comments
115.
by MarkusWinand 9y ago
The mentioned proof is confirming SQL:2003. See also: https://wiki.postgresql.org/wiki/Cyclic_Tag_System
116.
by MarkusWinand 9y ago
Not to forget SQLite: https://sqlite.org/lang_with.html
117.
by MarkusWinand 9y ago
PostgreSQL being the one noteworthy: http://modern-sql.com/feature/with/performance
118.
by MarkusWinand 9y ago
Related posts from the past: What ORMs have taught me: just learn SQL http://woz.posthaven.com/what-orms-have-taught-me-just-learn... ORM Is an Offensive Anti-Pattern http://www.yegor256.com/2014/12&#x2
119.
The case against ORMs(korban.net)
5 points by MarkusWinand 9y ago|1 comments
120.
by MarkusWinand 9y ago
I've added the other frameworks. As for the update marker, I've just added an "updated" date to next the the publishing date in the breadcrumb.

More ›