Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.5.40, 5.5.41
-
Fix Version/s: 5.5.42
-
Component/s: Storage Engine - InnoDB, Storage Engine - XtraDB
-
Labels:None
-
Environment:Ubuntu 14.04
Description
When I'm trying to create such tables server is killed. Logs in attachment
Checked on two computers.
CREATE TABLE orders_products
(
id INT PRIMARY KEY NOT NULL AUTO_INCREMENT,
orders_id INT UNSIGNED NOT NULL,
products_id TINYINT NOT NULL,
quantity SMALLINT UNSIGNED DEFAULT 0,
base_price DECIMAL(8,2) DEFAULT 0.00 NOT NULL,
amount DECIMAL(8,2) DEFAULT 0.00 NOT NULL,
FOREIGN KEY (orders_id) REFERENCES orders (id) ON DELETE RESTRICT ON UPDATE CASCADE,
FOREIGN KEY (products_id) REFERENCES products (id) ON DELETE RESTRICT ON UPDATE CASCADE
);
CREATE TABLE dashboard
(
id INT UNSIGNED PRIMARY KEY NOT NULL AUTO_INCREMENT,
created DATETIME NOT NULL,
createdby MEDIUMINT UNSIGNED NOT NULL,
modified DATETIME NOT NULL,
modifiedby MEDIUMINT UNSIGNED NOT NULL,
profiles_id INT UNSIGNED,
profiles_bookings_id INT UNSIGNED,
status TINYINT DEFAULT 0,
FOREIGN KEY (createdby) REFERENCES users (id) ON UPDATE CASCADE,
FOREIGN KEY (modifiedby) REFERENCES users (id) ON UPDATE CASCADE,
FOREIGN KEY (profiles_id) REFERENCES profiles (id) ON UPDATE CASCADE,
FOREIGN KEY (profiles_bookings_id) REFERENCES profiles_bookings (id) ON UPDATE CASCADE
);
I was trying already to drop database, recreate, etc.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Thanks, problem repeatable.
Ok, fix found, is your database secred or can I use it on test case ?
Do you need whole database or only few tables?
revno: 4420
committer: Jan Lindström <jplindst@mariadb.org>
branch nick: 5.5
timestamp: Wed 2015-02-04 14:40:46 +0200
message:
MDEV-7538: Wrong constraint (TINYINT or MEDIUMINT and INT)
causes server crash
Analysis: If wrong data types used on foreign constraint there
was possibility that foreign->id is NULL when incorrect
foreign constraint was removed from the dictionary cache.
Fix: Add guard foreign->id != NULL before trying to lookup
or remove the foreign constraint from dictionary cache.
Tested using user database where problem was repeatable.
Hi,
Please paste the output that you get in the client when you try to execute the statements; paste or attach the output of SHOW VARIABLES statement and your server error log.
Thanks.