Page MenuHomePhabricator

Recommend STRICT_ALL_TABLES for every install, not just development installs
ClosedPublic

Authored by epriestley on Feb 23 2014, 6:07 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Apr 23, 5:19 PM
Unknown Object (File)
Fri, Apr 19, 4:54 PM
Unknown Object (File)
Mon, Apr 15, 4:28 PM
Unknown Object (File)
Thu, Apr 11, 5:38 PM
Unknown Object (File)
Sun, Apr 7, 8:08 PM
Unknown Object (File)
Sun, Apr 7, 11:25 AM
Unknown Object (File)
Sun, Apr 7, 10:31 AM
Unknown Object (File)
Sun, Apr 7, 6:44 AM
Subscribers

Details

Summary

See D8308. Enabling STRICT_ALL_TABLES prevents this entire class of error, by fataling on truncation instead of truncating. We never want truncation; it is always bad and sometimes extremely bad.

We've recommended this mode for developer installs for a long time, and some users run with it enabled, so it's very unlikely to cause any issues (I've had it enabled locally for at least 6-8 months, I think).

Test Plan
  • Disabled mode.
  • Saw warning.
  • Enabled mode.
  • No warning.

{F117040}

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

Just enabled on our production instance.

{F117053}