3 ms·
This all depends on whether you have a database shared between different applications of business or whether you have a start-up where the application pretty mu
by joe_the_user 17y ago
This all depends on whether you have a database shared between different applications of business or whether you have a start-up where the application pretty much is the business.
In the later case, (web start-up), it makes sense to pare down the DB logic as needed and have application logic do everything from archiving to record locking. Of course, if your website does real financial stuff, you are going to have be super serious about writing routines that keep everything in the legally required formats, no small job.
In the former case, (traditional business with multiple apps), a serious database is designed to have what the organization needs. You shouldn't have a particular app trying to maintain either the ACID quality of DB or do archiving etc (unless the app is a script or utility run by the DBA). The database should be doing that for you.
-- And so, a lot of this debate comes because the debaters aren't considering the larger situation they are a part of.