4 ms·
> But in all of the sane systems I know, at the end of the day it’s really all “when”. Aren't databases basically "where"?
by dnautics 5y ago
> But in all of the sane systems I know, at the end of the day it’s really all “when”.
Aren't databases basically "where"?
- hinkley 5y agoOnly if your logic is all stored procedures. It doesn’t matter what the database says if you mangle the read operation.
- hypertele-Xii 5y agoWhat if the database itself contained all business logic? (but no plumbing) Every table has a function that is the only function that can write/insert into that table. The functions themselves are just records in a specific table, which the database schedules to run based on global access activity (it prefers to prioritize functions that consume more records than they produce, to keep space tight).