Ciro Santilli @cirosantilli  40

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.

Cool dude. Uses Stack Exchange: physics.stackexchange.com/users/31790/danielsank

Started at Google Quantum AI in 2014.

Has his LaTeX notes at: github.com/DanielSank/theory. One day he will convert to OurBigBook.com. Interesting to see that he is able to continue his notes despite being at Google.

This is a good read: quantumai.google/hardware/datasheet/weber.pdf May 14, 2021. Their topology is so weird, not just a rectangle, one wonders why! You get different error rates in different qubits, it's mad.

Got it working as mentioned at: github.com/cirosantilli/feathers-chat/tree/sequelize-pg

One major step was to port to PostgreSQL as shown at feathers-chat PostgreSQL.

Bibliography:

There's also a heroku branch at: github.com/feathersjs/feathers-chat/tree/heroku, but it also seems to use NeDB? So you can have a filesystem in Heroku? Doesn't seem so: stackoverflow.com/questions/42775418/heroku-local-persistent-storage

Bibliography:

gothinkster/realworld implementations based on Express.js.