Hudson, now there is a name I haven’t heard in a very long time.

Recently switched to a new contract, which resulted in me switching from IDEA Ultimate to vscode. This picture is terribly accurate.

In intellij I usually do code reviews by checking out the code and comparing the branch to origin/main to step through the changes. Just a right click menu option to compare branches.

I took for granted that this is just a thing IDEs should do, so I looked in vain for a while before googling it and finding out I need a plugin for that. (If I’m wrong please help me find the button, I still believe it must be in there somewhere. Surely the owners of GitHub can compare branches?)

A lot of companies have been doing this for years. AWS literally sells this as a service: https://www.mturk.com/

If you are searching by a primary key or other indexed id you should be fine. Here are a couple of articles to check out:

https://www.atlassian.com/data/databases/how-does-indexing-work

https://www.red-gate.com/simple-talk/featured/postgresql-indexes-what-they-are-and-how-they-help/

The TLDR is a where clause that hits an index doesn’t have to go through all the rows in the table.

I plan on being dead then, so do what you want with my digital wake.

“They simply go through the whole table”… that’s the problem. A full table scan should be avoided at all costs.

Learn: how to run and read an explain plan, indexes, keys, constraints, and query optimization (broadly you want to locate individual records as quickly as possible by using the most selective criteria).

You also need to learn basic schema design and to familiarize yourself with normalization.

Avoid processing huge result sets in your application. The database is good at answering questions about data it contains. It isn’t just a big bucket to throw data into to retrieve later.