when they start toddling around. Then they become kneebiters

Then she's at least a kneebiter by now! I need a diagram or something

sprog -> rugrat -> knee biter -> child?

that is a nicely done mohawk. Good use of superglue

not really sure... it's been a few months since we were looking - there wasn't much supply around then, but we went with a new-build, which bucks the market trend

(i.e. while existing owners were not putting their houses on the market, new-build developers were markedly enthusiastic to sell)

amazing isn't it.... still a bit of day light left at that time of day.

Yeah, it always surprise me. There are no white nights here but still the light is visible from the distance.

how far north was this? (roughly)

I can share exact location: https://maps.app.goo.gl/b66NxuWSt6XBwggo7

that isn't even that much further north from where I am.

How does it suppose to improve query planner? I always think if you have data stored in a single JSONB column, you probably should look at MongoDB 🙂

@U04V4KLKC postgresql doesn't collect stats on JSONB contents - so join decisions on JSONB indexes may be poor

yeah, I know, and extracting some fields to dedicated columns will help in the short term. But in general, I think such a schema is not a good idea. In a long run, you will have to take care of syncing those columns with the content of primary JSONB column, heavy\non-trivial migration will be needed every time you need yet another column for indexing, etc.

hmm. i've used a similar approach for SQLite dbs on the client side, and it's worked out very well - but in those cases the response to any schema changes was to throw away the table and fetch from the API again...

that's technically feasible in this case too, since i'm looking at an event-sourced architecture and i could certainly recreate a table from scratch - but that would be a lot of work just to add a key

maybe mongo is a good idea... though i didn't really enjoy the experience last time i tried to use it (which was quite some time ago)

xtdb/2 would be a good fit i think, were it ready

mongo db has the advantage of being web scale /s

... but /dev/null is even better ?

scalable for writes anyway.

GDPR compliant? Any stored data is correct. Preserves your right to be forgotten

AAAS - amnesia as a service