Opened 7 years ago

Closed 7 years ago

#16783 closed New feature (wontfix)

Don't validate models on runfcgi

Reported by: Ivan Sagalaev Owned by: Ivan Sagalaev
Component: Core (Management commands) Version: 1.3
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


runfcgi now requires model validation. However in production validation does more harm than it helps. It prevents site from starting up at all and showing any useful information (a pretty 500.html or partially working site). Besides, production is not the best place to debug validation errors anyway.

I think simply dropping model validation on runfcgi is a good solution.

Change History (1)

comment:1 Changed 7 years ago by Ivan Sagalaev

Resolution: wontfix
Status: newclosed

Talked to Jacob. A summary:

  • The situation I'm trying to work around with dropping model validation is not having a DB immediately available to do validation. For example your master DB is down and the site should be able to start to make a decision to switch to a slave.
  • Jacob's point is that it's a less common situation than the one when it's useful to have a last point check that DB in production is not broken.
  • A particular situation is easily fixable by inheriting a custom command with requires_model_validation=False and using that instead of the stock runfcgi.

Decision: WONTFIX

Note: See TracTickets for help on using tickets.
Back to Top