3 ms·
> New nullable columns are kryptonite to large Corrosion tables: cr-sqlite needs to backfill values for every row in the table Is this a typo? Why does it back
by soamv 11mo ago
> New nullable columns are kryptonite to large Corrosion tables: cr-sqlite needs to backfill values for every row in the table
Is this a typo? Why does it backfill values for a nullable column?
- andrewaylett 11mo agoI assume it would backfill values for any column, as a side-effect of propagating values for any column. But nullable columns are the only type you can add to a table that already contains rows, and mean that every row immediately has an update that needs to be sent.
- candiddevmike 11mo ago[flagged]
- tptacek 11mo agoNot a word of that article came from an LLM. You just don't like my writing. You think an LLM would have started a sentence with "Which is why that’s how"? Only me, baby.
- sroussey 11mo agoThere has been a period of call-out-ai-slop-for-upvotes here for a while that people may have bots just randomly posting such accusations. Love your response!
- ricardobeat 11mo agoIt seems to be a quirk of cr-sqlite, it wants to keep track of clock values for the new column. It's not backfilling the field values as far as I understand. There is a comment mentioning it could be optimized away: https://github.com/vlcn-io/cr-sqlite/blob/891fe9e0190dd20917f807d739c809e1bc32f6a3/core/rs/core/src/backfill.rs#L172-L179 https://github.com/vlcn-io/cr-sqlite/blob/891fe9e0190dd20917...