3 ms·
That's what ON UPDATE CASCADE is for. If you have a distributed system, generating unique identifiers and keeping referential consistency across the distribute
by wulczer 15y ago
That's what ON UPDATE CASCADE is for.
If you have a distributed system, generating unique identifiers and keeping referential consistency across the distributed parts is already a difficult problem. But that's a digression. If I ever get so many users I'll have to partition the user table across databases, I'll have much more trouble that just their IDs (and I'll be rich :) )
- wladimir 15y agoYes, but in practice it frequently happens that you refer to records in various different places. Either client-side in API-using software, or in a completely separate database, etc. In such cases, "Update all references in the world" will be entirely impractical and bug-prone.