Have a look at some interesting examples under nodejs/sequelize/raw/many_to_many.js.

Head of the theoretical division at the Los Alamos Laboratory during the Manhattan Project.

Richard Feynman was working under him there, and was promoted to team lead by him because Richard impressed Hans.

He was also the person under which Freeman Dyson was originally under when he moved from the United Kingdom to the United States.

And Hans also impressed Feynman, both were problem solvers, and liked solving mental arithmetic and numerical analysis.

This relationship is what brought Feynman to Cornell University after World War II, Hans' institution, which is where Feynman did the main part of his Nobel prize winning work on quantum electrodynamics.

Hans must have been the perfect PhD advisor. He's always smiling, and he seemed so approachable. And he was incredibly capable, notably in his calculation skills, which were much more important in those pre-computer days.

UPSERT is extremely handy, and reduces the number of find, check on server, update loops. But RETURNING is a fundamental part of that (to get the updated/existing) ID. Can't believe SQL hasn't standardized it yet as of 2022. But both SQLite and Postgres support it with similar syntax thankfully.

Attempt at nodejs/sequelize/raw/upsert.js:

Related on more complex constraints:

youtu.be/oCelMyMtRCk?t=167 mentions that they get their lipid layer from the Golgi complex of the host, where they replicate.

An example where SELECT FOR UPDATE is a good solution to an use case can be seen at: nodejs/sequelize/raw/parallel_select_and_update.js.

SELECT FOR UPDATE vs/together with the SQL transaction isolation level is commented at: stackoverflow.com/questions/10935850/when-to-use-select-for-update.

SQL's implementation of database triggers.

This feature is really cool, as it allows you to keep caches up to date!

In particular, everything that happens in a trigger happens as if it were in a transaction. This way, you can do less explicit transactions when you use triggers. It is a bit like the advantages of SQL CASCADE.

DBMS:

ORM:

TODO what is the standard compliant syntax?

PostgreSQL requires you to define a SQL stored procedure: stackoverflow.com/questions/28149494/is-it-possible-to-create-trigger-without-execute-procedure-in-postgresql Their syntax may be standard compliant, not sure about the EXECUTE part. Their docs: www.postgresql.org/docs/current/sql-createtrigger.html

SQLite does not support SQL stored procedures at all, so maybe that's why they can't be standard compliant here: stackoverflow.com/questions/3335162/creating-stored-procedure-in-sqlite

SQL:1999 11.38 covers "Trigger definition". The Abstract syntax tree starts with the CREATE TRIGGER and ends in:

This is defined at 13.5 "SQL procedure statement", but that is humongous and I'm not sure what it is at all.

Why is it there such a clear separation of phases?

Why do people with mild symptoms go on to die? It is a great mystery.

Ciro Santilli's theory is that COVID is extremely effective at avoiding immune response. Then, in people where this is effective, things reach a point where there is so much virus, that the body notices and moves on to take a more drastic approach. This is compatible with the virus killing older people more, as they have weaker immunes systems. This is however incompatible with the fact that people don't seem to be contagious after the viral phase is over...

In this example we cache track the number of posts per user on a cache column.

Basic example tested on SQLite 3.40.1, Ubuntu 23.04:output:

Two columns two rows:output:

Note how duplicates are removed, to keep them we UNION ALL instead:output: