3 ms·
It all depends on how much of your "program" lives in the database, in terms of things like triggers, stored functions, etc. That's the argument against those
by paulmd 10y ago
It all depends on how much of your "program" lives in the database, in terms of things like triggers, stored functions, etc.
That's the argument against those things - it makes it difficult to switch your database. But there are also some compelling performance arguments in some cases, so in a well-designed system those parts of the code that live in the DB also tend to be important ones.
- rbanffy 10y agoThis is pretty much the kind of "wrong" I meant. ;-) In this case, it's still wrong, but faster than doing it right.
- flukus 10y ago> That's the argument against those things - it makes it difficult to switch your database. But there are also some compelling performance arguments in some cases, so in a well-designed system those parts of the code that live in the DB also tend to be important ones. But if they only exist for the critical parts then porting is a lot easier.