I'm excited about this! There are times when a derived data column is the only way to get acceptable query performance (normalisation be damned!) and previously that's meant either handling it in...
I'm excited about this! There are times when a derived data column is the only way to get acceptable query performance (normalisation be damned!) and previously that's meant either handling it in app logic and condemning yourself to potential inconsistency, or writing triggers that seem as though they're perfectly robust until a grey-bearded DBA/wizard points out an obscure potential race condition.
This basically looks like an update trigger that's backed with all the guarantees of the database engine itself, which is very useful indeed.
I honestly thought this was about queries with derived data columns before you wrote this comment. Now I see that this is very useful indeed, and it also helps to make the JSONB datatype more...
I honestly thought this was about queries with derived data columns before you wrote this comment.
Now I see that this is very useful indeed, and it also helps to make the JSONB datatype more useful in general IMHO.
I'm excited about this! There are times when a derived data column is the only way to get acceptable query performance (normalisation be damned!) and previously that's meant either handling it in app logic and condemning yourself to potential inconsistency, or writing triggers that seem as though they're perfectly robust until a grey-bearded DBA/wizard points out an obscure potential race condition.
This basically looks like an update trigger that's backed with all the guarantees of the database engine itself, which is very useful indeed.
I honestly thought this was about queries with derived data columns before you wrote this comment.
Now I see that this is very useful indeed, and it also helps to make the JSONB datatype more useful in general IMHO.