Is that what the three seashells are?

Aw rats.

Have tried to exterminate Jordan Peterson recommendations for years to no avail.

I wonder if YouTube lets these plugins through because it doesn’t want to attract antitrust suits

https://m.youtube.com/watch?v=K44j-sb1SRY

https://m.youtube.com/watch?v=6YHEK6-Ili8

Beer is oddly terrible and weak in Australia but Toohey’s Old is good, more rare down here in Vic though

Mods you might want to remove this due to no politics, I will myself if you dont

Didn’t even think of that. You’re right.

Dual citizen with Australia, sorry. Though it is fairly light paperwork for Americans who are in tech - as in the U.S., the best chances are to get in stateside with a big company that has an Aussie HQ (Atlassian, Xero, Canva, FAANG, etc.) and then transfer

I left and got two Sr SWE positions within 3 months. It’s like the 90’s down here

I’m actually removing this myself because the rule is no politics

I’m going to try. Could be:

1. A long running UPDATE which can temporarily lock all of the data that is being updated. Basically a lock is when the relevant data is frozen while the transaction executes. This can happen at the field or row or table level in most robust database management systems, but in SQLite, during the time when a create, update, or delete is actually being written to disk, the whole file (database) is locked while that happens, even for processes wishing to perform reads.

The solution is to wait for completion, but your query could take 7 million years to complete so… you might not have the patience. You could also just exhaust the compute/memory resources of the machine.

This feels bad when you expected it to be a simple transaction or when you only expected the update to apply to a small subset of data… it’s possible that you’re using a suboptimal query strategy (e.g. many JOINs, lack of indices, not using WITH) or that you’re running your UPDATE on a huge number of records instead of the three you expected to change.

And/or

2. A deadlock, meaning the same data is being operated on at the same time, but the operations can’t execute because there is a competing/circular lock.

The use of BEGIN means that the transaction has started. You usually use COMMIT to actually finish and complete the transaction. If you’ve got another query operating on the same data happening during this time, even if it’s data that is incidental and only used to make the JOIN work, there can be “overlap” which makes the transactions hang, because the DB engine can’t work out which lock to release first.

SQLite is single file based and has a more basic and broad lock vs Postgres or other DMBSes. This means that SQLite doesn’t deadlock because it processes each transaction one after another, but this paradigm may slow everything down vs. MariaDB, Postgres etc

Also see ACID compliance for further reading (https://en.wikipedia.org/wiki/ACID)

All my homies work at Lawrence Livermore

I believe you just described MCP

And Australia! And I am from both.