ModernSQL's profile picture. Still using Windows 3.1? So why stick to SQL-92? A lot has changed in 30 years. We embrace the standard.

Modern SQL

@ModernSQL

Still using Windows 3.1? So why stick to SQL-92? A lot has changed in 30 years. We embrace the standard.

Modern SQL 님이 재게시함

After being « gone fishin' » during summertime I just updated my website for the releases that happened during that time: * MariaDB 11.8 and 12.0 * Oracle 23.9 * Db2 12.1.2 All charts on modern-sql.com and use-the-index-luke.com are updated.


Just updated modern-sql.com and use-the-index-luke.com for MariaDB 11.7. One enhancement is the FROM-clause column renaming, as described in this article: modern-sql.com/caniuse/E051-09


Modern SQL 님이 재게시함

A Christmas present for SQL standard lovers? Part 1 is available for free again. standards.iso.org/ittf/PubliclyA… The last edition that was available for free was 2011, AFAIK. And that disappeared when 2016 was released. Merry Christmas :)


Modern SQL 님이 재게시함

The scraping of content for AI training makes some changes required. I'll publish less on my website and RSS feed. The mailing lists will probably stay the same for the time being. If you want to still get everything, subscribe here: winand.at/lists


Modern SQL 님이 재게시함

Would you miss Apache Derby when I would remove it from the charts on modern-sql.com?


Modern SQL 님이 재게시함

While the BMP covers the need of most living languages, it lacks support for symbols that made it into informal language (emojis). Always test your code & engine with non-BPM characters. Ideally one which needs four bytes in the UTF-8 encoding. Here is one for easy c&p: 💩


Modern SQL 님이 재게시함

SQL's data types CHAR and VARCHAR are about characters. Sounds like a no-brainer, doesn't it? Well, a consequence is that the number in the parenthesis refer to characters, not bytes. Unfortunately, some SQL engines don't get that right—causing major confusion among users.

ModernSQL's tweet image. SQL's data types CHAR and VARCHAR are about characters. Sounds like a no-brainer, doesn't it?

Well, a consequence is that the number in the parenthesis refer to characters, not bytes.

Unfortunately, some SQL engines don't get that right—causing major confusion among users.

Loading...

Something went wrong.


Something went wrong.