Comment by lazide
1 month ago
What way of making it better supported wouldn’t require custom semantics that people would forget and then select the wrong thing.
1 month ago
What way of making it better supported wouldn’t require custom semantics that people would forget and then select the wrong thing.
> custom semantics
Making those custom semantics (enabled at per-schema/per-table level) take over what was already there previously: DELETE doing soft-deletes by default and SELECT only selecting the records that aren't soft deleted, for example.
Then making the unintended behavior (for 90% of normal operational cases) require special commands, be it a new keyword like DELETE HARD or SELECT ALL, or query hints (special comments like /*+DELETE_HARD*/).
Maybe some day I'll find a database that's simple and hackable enough to build it for my own amusement.