3 ms·
> I would generally advocate for no write access outside of the app as well. FWIW I think OP was referring to app code still, but code opting in to skipping ap
by corytheboyd 2y ago
> I would generally advocate for no write access outside of the app as well.
FWIW I think OP was referring to app code still, but code opting in to skipping app data validations. Rails for example makes this very easy to do, and there are tons and tons of people out there selling this as a performance improvement (this one trick speeds up bulk operations!!!!). There are times where it’s useful, but it’s a very sharp knife that people can easily misuse.
So yeah, anyway, have both db constraints and app validations.
- goosejuice 2y agoThanks for pointing that out, I did misread that and have seen/written such things in rails land. We used active record import which gives the option of running validations. But yeah, layering your safety nets is generally wise. I would include testing and code review in that as well.