Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • Your answer assumes that the OP actually has the ability to fix the database. Commented Aug 8, 2016 at 16:45
  • Great points.. keeping things in sync is probably the biggest argument against trying to make a smart DAL. I continue to be bothered by allowing code to perform actions which violate integrity (specifically because this app had poor database protections to begin with) but the smart move would be to attack the root of the problem (which would be issues in the database). Commented Aug 8, 2016 at 16:47
  • @RobertHarvey A temporary junior DBA could help. Maintenance of a codebase is costly. The more code is business layer oriented or final user oriented, the better. Investing programming time in mundane tasks as making sure no duplicates are inserted in PK-less tables or a non-related row inserted in a FK-less table is a waste of developer's time. Which is expensive. Commented Aug 8, 2016 at 16:56