mirror of
https://we.phorge.it/source/phorge.git
synced 2024-11-11 17:32:41 +01:00
bbf40146fb
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} Reviewers: btrahan, chad Reviewed By: chad CC: chad, aran, arice Differential Revision: https://secure.phabricator.com/D8309
63 lines
2.6 KiB
PHP
63 lines
2.6 KiB
PHP
<?php
|
|
|
|
final class PhabricatorSetupCheckMySQL extends PhabricatorSetupCheck {
|
|
|
|
protected function executeChecks() {
|
|
$conn_raw = id(new PhabricatorUser())->establishConnection('w');
|
|
|
|
$max_allowed_packet = queryfx_one(
|
|
$conn_raw,
|
|
'SHOW VARIABLES LIKE %s',
|
|
'max_allowed_packet');
|
|
$max_allowed_packet = idx($max_allowed_packet, 'Value', PHP_INT_MAX);
|
|
|
|
$recommended_minimum = 1024 * 1024;
|
|
if ($max_allowed_packet < $recommended_minimum) {
|
|
$message = pht(
|
|
"MySQL is configured with a very small 'max_allowed_packet' (%d), ".
|
|
"which may cause some large writes to fail. Strongly consider raising ".
|
|
"this to at least %d in your MySQL configuration.",
|
|
$max_allowed_packet,
|
|
$recommended_minimum);
|
|
|
|
$this->newIssue('mysql.max_allowed_packet')
|
|
->setName(pht('Small MySQL "max_allowed_packet"'))
|
|
->setMessage($message);
|
|
}
|
|
|
|
$mode_string = queryfx_one($conn_raw, "SELECT @@sql_mode");
|
|
$modes = explode(',', $mode_string['@@sql_mode']);
|
|
if (!in_array('STRICT_ALL_TABLES', $modes)) {
|
|
$summary = pht(
|
|
"MySQL is not in strict mode, but using strict mode is strongly ".
|
|
"encouraged.");
|
|
|
|
$message = pht(
|
|
"On your MySQL instance, the global sql_mode is not set to ".
|
|
"'STRICT_ALL_TABLES'. It is strongly encouraged that you enable this ".
|
|
"mode when running Phabricator.\n\n".
|
|
"By default, MySQL will fail silently and continue when certain ".
|
|
"error conditions occur. Sometimes contuining does the wrong thing. ".
|
|
"For example, inserting too much data into a column will cause ".
|
|
"silent truncation (and thus data loss) instead of failing in an ".
|
|
"obvious way that we can fix. These behaviors can also create ".
|
|
"security risks. Enabling strict mode raises an explicit error ".
|
|
"instead and prevents this entire class of problem from doing any ".
|
|
"damage.\n\n".
|
|
"You can find more information about this mode (and how to configure ".
|
|
"it) in the MySQL manual. Usually, it is sufficient to add this to ".
|
|
"your 'my.cnf' file:\n\n".
|
|
"%s\n".
|
|
"(Note that if you run other applications against the same database, ".
|
|
"they may not work in strict mode. Be careful about enabling it in ".
|
|
"these cases.)",
|
|
phutil_tag('pre', array(), 'sql-mode=STRICT_ALL_TABLES'));
|
|
|
|
$this->newIssue('mysql.mode')
|
|
->setName(pht('MySQL STRICT_ALL_TABLES Mode Not Set'))
|
|
->setSummary($summary)
|
|
->setMessage($message);
|
|
}
|
|
}
|
|
|
|
}
|