> Many constraints are extremely expensive to enforce at scale to the point of being prohibitive
Incremental View Maintenance engines might be the solution we've been waiting for here.
Incremental View Maintenance engines might be the solution we've been waiting for here.
…and the lack of a LEFT OUTER JOIN also kills it for a lot of things too.
One problem is that a Txn won’t commit until all secondary indexes are updated, but I’d prefer it if there was a way for a Txn to unblock its caller once the base-table update is saved; updates to secondary indexes could then continue asynchronously. (I know this is hardly an original idea, but I haven’t read why this can’t be done)