LoneWolf123

Back in the day I used to be among top users on that site - they even sent me a T-shirt at some time. Left several years ago, as the site became toxic.

I'm not mentioning this "top user" thing on my resume anymore, because not relevant.

The site is still an excellent source of information about all things that were cool ten years ago, such as Java, Spring, SQL, Python.

This might be excellent: fully implemented MERGE in other RDBMS seemed to be highly unreliable. Given Postgres' focus on quality, not on number of features, not implementing MERGE fully might be a great choice.

Just imagine how many permutations we'd need to unit test the implementation of full MERGE. Sounds scary. Better develop a frequently used subset, the UPSERT, and stop at that.

Isn't it a breaking change? Using WITH subqueries to fence off query planner seemed to be a thing, right?

Is it curable? Has your eyesight been restored?

1. Postgres does provide natural joins:

http://www.postgresqltutorial.com/postgresql-natural-join/

2. Not all joins can be inferred like this:

` FROM People AS p JOIN Age_Groups AS ag ON ag.min_age <= p.age AND p.age < ag.max_age`

What about Linux laptops? Are you considering that alternative?

You may want to use this small script: "Like 'go get' but with pinned package versions. A tiny shell script".

https://github.com/joewalnes/go-getter

In Chicago, storm sewers would definitely contain human waste.