Результаты опроса аудитории StackOverflow по используемым СУБД. Удивляет популярность узкоприменимой SQLite.

Машка с муськой вместе дают огромный перевес. Постгри, конечно, уверенно тащит, хотя раньше никто не верил.

Time to update my open source SQL tools collection!

Yet another one SQL killer (modern language for transforming data — a simple, powerful, pipelined SQL replacement). Written in RUST :)

https://github.com/prql/prql

I call the police!

https://www.twilio.com/blog/sqlite-postgresql-complicated

absolutely cursed…

+1 mysql based DB:

https://github.com/stoneatom/stonedb

To distract from the problem, I randomly deleted 5 rows from the table.... :)))

https://www.cybertec-postgresql.com/en/transaction-anomalies-with-select-for-update/

Postgres 15 improves UNIQUE and NULL

https://blog.rustprooflabs.com/2022/07/postgres-15-unique-improvement-with-null

a better way now…

English to RegEx with Natural Language Processing:
autoregex.xyz

next year in postgres:

https://twitter.com/nori_shinoda/status/1549683794780622848

SQL-WTF SQL-TIL

A few words about this.
At this moment, you must specify an alias for all sub-selects in FROM clause.
It's valid for PostgreSQL and MySQL.

In Snowflake you can skip it. But under the hood Snowflake name it automatically as "values". So, you can't use more than one unnamed sub-select in FROM clause, because "values" will conflict. And yes, you can address it as "values".*

Btw, there are some more "automatic aliases" in Snowflake:
- "VALUES" (capital letters, not the same) for values()
- "STAGE" for stages
- "LIST_DIR_TABLE" for directory tables

Absolutely insane behavior with sub-selects (named or unnamed) in the best and most popular DB in the world (he-he) - SQLite!

select * from (select 1) a, (select 1) b
Try to guess without tests (post your version in the comments)

All issues of SQL-WTF SQL-TIL magazine
(so you can share it with friends and colleagues):

postgresql edition:
1) https://news.1rj.ru/str/nosingularity/535 (ru)
2) https://news.1rj.ru/str/nosingularity/541 (ru)
3) https://news.1rj.ru/str/nosingularity/548 (ru)
4) https://news.1rj.ru/str/nosingularity/572 (ru)

snowflake edition:
5) https://news.1rj.ru/str/nosingularity/582 (ru)
6) https://news.1rj.ru/str/nosingularity/602 (ru)
7) https://news.1rj.ru/str/nosingularity/753 (ru) + https://news.1rj.ru/str/nosingularity/754 (ru)
8) https://news.1rj.ru/str/nosingularity/762 (ru)
9) https://news.1rj.ru/str/nosingularity/826 (ru)

mix:
10) https://news.1rj.ru/str/nosingularity/755 (ru)
11) https://news.1rj.ru/str/nosingularity/803 (ru) + https://news.1rj.ru/str/nosingularity/804 (ru)
12) https://news.1rj.ru/str/nosingularity/808 (ru) + https://news.1rj.ru/str/nosingularity/809 (ru)
13) https://news.1rj.ru/str/nosingularity/857 (ru)
14) https://news.1rj.ru/str/nosingularity/1024 (en)

HAXE in a new way:
https://github.com/pfusik/cito

SQL-WTF SQL-TIL snowflake edition.

In Snowflake, you can create tables, stages, and functions temporarily.
Temporary objects remain visible in the current session only and disappear after the session ends.

The unusual behavior is that you can create a temporary object with the same name as an already existing object.

So, all existing objects linked with it will be relinked to the "new" temporary object. For e.g. all views dependent on the original table will depend on the temporary table.

More than it!

The permanent table created after the temporary table with the same name stays invisible in the current session too :)

OMG
https://github.com/oguimbal/pg-mem

Well ... then it's time to remind you about my collection of open source SQL-tools:
https://github.com/antonrevyako/useful-links/blob/master/opensource-sql-tools.md