4 ms·
>I have to disagree. You should always put limits on everything like any orthodoxy it should have a limit put on it. >But if there is multiple interfaces (suc
by VladRussian2 13y ago
>I have to disagree. You should always put limits on everything
like any orthodoxy it should have a limit put on it.
>But if there is multiple interfaces (such as a REST api etc) to your database then you have to remember to put them in place everywhere.
multiple interfaces going directly to database - that's a much bigger problem that the rest pales before it. In particular, multiple updates of limits would constitute only minor share of headache causing updates and the multiple updates itself would be just a minor share of the whole headache.
- Pxtl 13y agoGood God, yes. I've worked on too many older projects where all the old business logic lived in the database, and all the new business logic lived in the application, and keeping them sorted out was a nightmarish pain. The defense for using horrible database-specific procedural languages for all that business code was that it meant we could have one back-end for all the front-ends. I've seen this pattern so many times, and it's pure agony.