Does Stage work for PRs that have multiple commits? These could be considered "stacked diffs", but in the same PR.

Chapters are regenerated every time a new commit is pushed to a PR. Our thinking is that the chapters should serve as "auto stacked diffs" since they should follow a logical order.

Do you or your team use stacking in your workflows?

According to https://www.sfmta.com/getting-around/drive-park/how-avoid-pa...

> During street sweeping hours, you may not park until the street has been physically swept.

You might be able to use FILE_FLAG_DELETE_ON_CLOSE, but this would likely require calling the Windows API functions directly.

Trino no longer depends on Hadoop/Hive for any of its data lake connectors. Removing that dependency was a huge effort.

Yeah, URL is from the first release of Java and should be avoided. You want to use URI instead.

tbgs is internal code search for Facebook: https://codesearchguide.org/story/facebook

JLine has a complete terminal library and includes a demo which is a full editor: https://github.com/jline/jline3

Procedures are very useful to enforce business logic in the database, rather than in the application. It’s like putting a higher level application-specific API on top of your database schema.

For Cockroach, it could help substantially with latency for multi-statement transactions, since the procedure could be executed on a database node closest to the leaseholder for the data. Executing a multi-statement transaction on the client means incurring per-statement latency between the client and gateway node, and between the gateway node and the leaseholder.

It's also a bad idea.

$49 for the device and data: https://blues.io/

The H2 embedded database has compatibility modes for other databases, which seems helpful for testing, but ends up being incompatible in various ways for anything non-trivial. You end up fighting the compatibility and skipping useful native features of the target database, while still not having confidence that the code works on the target database.

We now use the awesome Testcontainers library (available for multiple languages) that makes it easy to launch the real database in a Docker container. Testing applications against multiple databases is now trivial.

Thanks, that's interesting and a really useful data point. :)