Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Why 'foreign key constraint fails' when foreign key exists?

I have a simple query

UPDATE `t_timecard_detail` SET  `timeoff_request_id` = 'adad8e0d-c22b-41c3-a460-6cf982729299' WHERE `id` = 'cfc7a0a1-4e03-46a4-af89-069a0661cf55'; 

which gives this error

ERROR 1452 (23000): Cannot add or update a child row: a foreign key constraint fails (`demo1_timeapp`.`t_timecard_detail`, CONSTRAINT `timeoff_request_id_refs_id_48fe5c4` FOREIGN KEY (`timeoff_request_id`) REFERENCES `t_timeoff_request` (`id`))

constraint is

CONSTRAINT `timeoff_request_id_refs_id_48fe5c4` FOREIGN KEY (`timeoff_request_id`) REFERENCES `t_timeoff_request` (`id`)

though the ID 'adad8e0d-c22b-41c3-a460-6cf982729299' exists in t_timeoff_request table

mysql> select `id`  from t_timeoff_request where `id`='adad8e0d-c22b-41c3-a460-6cf982729299';
+--------------------------------------+
| id                                   |
+--------------------------------------+
| adad8e0d-c22b-41c3-a460-6cf982729299 |
+--------------------------------------+

So I am not sure why mysql says 'foreign key constraint fails' when the foreign key exists?

mysql version:

$ mysql --version
mysql  Ver 14.14 Distrib 5.1.41, for debian-linux-gnu (i486) using readline 6.1

Edit: Looks like one table has ENGINE=MyISAM and other innodb

output of show create table t_timecard_detail;

CREATE TABLE `t_timecard_detail` (
  `id` varchar(36) NOT NULL,
  `change_time` datetime NOT NULL,
  `department_id` varchar(36) DEFAULT NULL,
  `day` date NOT NULL,
  `in_punch_id` varchar(36) DEFAULT NULL,
  `punch_in` datetime DEFAULT NULL,
  `paid_in` datetime DEFAULT NULL,
  `infraction_in_id` varchar(36) DEFAULT NULL,
  `schedule_in` datetime DEFAULT NULL,
  `type_in` varchar(10) NOT NULL,
  `out_punch_id` varchar(36) DEFAULT NULL,
  `punch_out` datetime DEFAULT NULL,
  `paid_out` datetime DEFAULT NULL,
  `schedule_out` datetime DEFAULT NULL,
  `infraction_out_id` varchar(36) DEFAULT NULL,
  `type_out` varchar(10) NOT NULL,
  `work_min` int(11) NOT NULL,
  `ot_min` int(11) NOT NULL,
  `ot2_min` int(11) NOT NULL,
  `pay_type_id` varchar(36) NOT NULL,
  `timecard_id` varchar(36) NOT NULL,
  `user_entered` tinyint(1) NOT NULL,
  `comments` varchar(256) DEFAULT NULL,
  `timeoff_request_id` varchar(36),
  PRIMARY KEY (`id`),
  KEY `t_timecard_detail_department_id` (`department_id`),
  KEY `t_timecard_detail_in_punch_id` (`in_punch_id`),
  KEY `t_timecard_detail_infraction_in_id` (`infraction_in_id`),
  KEY `t_timecard_detail_out_punch_id` (`out_punch_id`),
  KEY `t_timecard_detail_infraction_out_id` (`infraction_out_id`),
  KEY `t_timecard_detail_pay_type_id` (`pay_type_id`),
  KEY `t_timecard_detail_timecard_id` (`timecard_id`),
  KEY `t_timecard_detail_4f5ffbb5` (`timeoff_request_id`),
  CONSTRAINT `department_id_refs_id_1b23ee35` FOREIGN KEY (`department_id`) REFERENCES `t_department` (`id`),
  CONSTRAINT `infraction_in_id_refs_id_17b2e173` FOREIGN KEY (`infraction_in_id`) REFERENCES `t_pay_group_infraction` (`id`),
  CONSTRAINT `infraction_out_id_refs_id_17b2e173` FOREIGN KEY (`infraction_out_id`) REFERENCES `t_pay_group_infraction` (`id`),
  CONSTRAINT `in_punch_id_refs_id_4d13a8b2` FOREIGN KEY (`in_punch_id`) REFERENCES `t_punch` (`id`),
  CONSTRAINT `out_punch_id_refs_id_4d13a8b2` FOREIGN KEY (`out_punch_id`) REFERENCES `t_punch` (`id`),
  CONSTRAINT `pay_type_id_refs_id_70cb7404` FOREIGN KEY (`pay_type_id`) REFERENCES `t_pay_type` (`id`),
  CONSTRAINT `timecard_id_refs_id_7889236c` FOREIGN KEY (`timecard_id`) REFERENCES `t_timecard` (`id`),
  CONSTRAINT `timeoff_request_id_refs_id_48fe5c4` FOREIGN KEY (`timeoff_request_id`) REFERENCES `t_timeoff_request` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 

output of show create table t_timeoff_request;

CREATE TABLE `t_timeoff_request` (
  `id` varchar(36) NOT NULL,
  `change_time` datetime NOT NULL,
  `employee_id` varchar(36) NOT NULL,
  `submitted_date` datetime NOT NULL,
  `time_off_day` date NOT NULL,
  `mins_charged` int(11) NOT NULL,
  `pay_type_id` varchar(36) NOT NULL,
  `employee_comment` varchar(300) NOT NULL,
  `approved_status` varchar(10) NOT NULL,
  `approved_by_id` varchar(36) DEFAULT NULL,
  `approved_date` datetime DEFAULT NULL,
  `approved_comment` varchar(300) DEFAULT NULL,
  PRIMARY KEY (`id`),
  KEY `t_timeoff_request_employee_id` (`employee_id`),
  KEY `t_timeoff_request_pay_type_id` (`pay_type_id`),
  KEY `t_timeoff_request_approved_by_id` (`approved_by_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1
like image 699
Anurag Uniyal Avatar asked Oct 08 '10 11:10

Anurag Uniyal


People also ask

Why do foreign key constraints fail?

The error comes when you are trying to add a row for which no matching row in in the other table. “Foreign key relationships involve a parent table that holds the central data values, and a child table with identical values pointing back to its parent. The FOREIGN KEY clause is specified in the child table.

How do you know if a foreign key constraint exists?

To check if a foreign key constraint exists on a table uses the system stored procedure named SP_FKEYS or view INFORMATION_SCHEMA.

What is violation of foreign key constraint?

Foreign key constraint violation occurred, dbname = database_name, table name = table_name, constraint name = constraint_name. Occurs when an insert or update on a foreign key table is performed without a matching value in the primary key table.

What is the difference between foreign key and foreign key constraint?

A foreign key joins a table to another table by referencing its primary key. A foreign key constraint specifies that the key can only contain values that are in the referenced primary key, and thus ensures the referential integrity of data that is joined on the two keys.

Can a foreign key reference another foreign key?

A foreign key can reference any field defined as unique. If that unique field is itself defined as a foreign key, it makes no difference. A foreign key is just to enforce referential integrity.

How can avoid foreign key constraint in SQL?

Use SQL Server Management StudioIn Object Explorer, expand the table with the constraint and then expand the Keys folder. Right-click the constraint and select Modify. In the grid under Table Designer, select Enforce Foreign Key Constraint and select No from the drop-down menu. Select Close.


2 Answers

I think it's a bug. MySQL shouldn't allow You to add FOREIGN KEY referencing to MyISAM table from InnoDB because MyISAM engine isn't transactional, InnoDb is.

Try:
ALTER TABLE t_timeoff_request ENGINE=InnoDB;
like image 142
baklarz2048 Avatar answered Sep 24 '22 02:09

baklarz2048


Foreign key constraints can't be applied to MyISAM engine.both table should use innodb engine for supporting foreign key constraints.

like image 28
Prakash Avatar answered Sep 24 '22 02:09

Prakash