diff options
author | Florian Pritz <bluewind@xinu.at> | 2017-04-15 20:31:38 +0200 |
---|---|---|
committer | Lukas Fleischer <lfleischer@archlinux.org> | 2017-04-16 10:35:49 +0200 |
commit | 102dad49e727059441d5566d317e8a57def08b2d (patch) | |
tree | 360cd9a8748f7fdc95411b569d31b82a1873cea6 | |
parent | 09cb61ab83af531a1b4ea43fd96313314d964726 (diff) | |
download | aur-102dad49e727059441d5566d317e8a57def08b2d.tar.gz aur-102dad49e727059441d5566d317e8a57def08b2d.tar.xz |
schema: Fix invalid NULL on primary key
>From the mysql 5.7 breaking change page:
Columns in a PRIMARY KEY must be NOT NULL, but if declared explicitly as
NULL produced no error. Now an error occurs. For example, a statement
such as CREATE TABLE t (i INT NULL PRIMARY KEY) is rejected. The same
occurs for similar ALTER TABLE statements. (Bug #13995622, Bug #66987,
Bug #15967545, Bug #16545198)
References:
http://stackoverflow.com/a/22314073
Signed-off-by: Florian Pritz <bluewind@xinu.at>
Signed-off-by: Lukas Fleischer <lfleischer@archlinux.org>
-rw-r--r-- | schema/aur-schema.sql | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/schema/aur-schema.sql b/schema/aur-schema.sql index b3e4ecbb..89167b32 100644 --- a/schema/aur-schema.sql +++ b/schema/aur-schema.sql @@ -373,7 +373,7 @@ CREATE TABLE IF NOT EXISTS TU_Votes ( -- Malicious user banning -- CREATE TABLE Bans ( - IPAddress VARCHAR(45) NULL DEFAULT NULL, + IPAddress VARCHAR(45) NOT NULL, BanTS TIMESTAMP NOT NULL, PRIMARY KEY (IPAddress) ) ENGINE = InnoDB; |