sourcesmith

If you want to include Postgres jsonb columns in that then a partial index of the expression of a NOT of the jsonb contains jsonb operator.

> > Their section on reliable replications can be resolved by keeping a log of the changes made to the database rather than a log of the queries.

> You'd need to define a representation of that log, which ends up being equivalent to writing a NoSQL datastore.

I think this covered by relational DBs redo/rollback/write-ahead log; whatever you want to call it.

And yet to have a card payment go through successfully via them...

Not just other squirrels. I have seen a magpie sitting on a wall waiting for a squirrel to finish burying its nut. Once the squirrel had finished, it descended to have a good poke around the burial area.

The only native mammals in New Zealand are bats and marine mammals.

I have never had a payment on a site using Stripe go through (having tried a number of cards). How are they still in business?

I am guessing vertical axis turbines do not have this bias but they only seem to be used in smaller designs?

There were a lot of Y2K related tasks in the course of many developers generally activity. Where I worked at the time, there were not developers solely dedicated to Y2K work. The Y2K issue pretty much caused an employment boom for software developers though.

"I could have run the process with cgroup and namespace isolation"... using systemd.

But it's expired...

That is another Amazon company so can we note expect the same shenanigans?

In reality, that would be GET /user GET settings; the cost for the unneeded associated fields at that point of time is typically not significant for many backends as they stored in aggregate and text based responses compress well.

If the data is not particular dynamic then you can cache the entire representation deriving a future benefit.

Graph base queries tend to lend themselves to adhoc query patterns and I would be concerned about unpredictable patterns of loading. If the backend store is distributed then graph QL looks more attractive to me. If the datastore stores related attributes in aggregate there seems to be little benefit since different parts of an adhoc graph would different levels of 'cachability'.

I have found an application for GraphQL in storing soft-defined triggers or other criteria on data.

I think this has already been addressed by the sibling comment to my question. Insulation does not have to impermeable. Its purpose to prevent the loss of air carrying heat with it, not the transfer of moisture/humidity.

Have you looked at thermodynamic panels?