Drop sakila causes error: annot delete or update a parent row: a foreign key constraint fails

Bug #378222 reported by Paul McCullagh on 2009-05-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Vladimir Kolesnikov

Bug Description

Hi Paul,
While testing MariaDB, I cam across a bug that affects PBXT.

Operating system: Mac OSX. Compiled with:
#! /bin/sh

path=`dirname $0`
. "$path/SETUP.sh"

extra_flags=" $fast_cflags $max_cflags -g"
extra_configs=" $max_no_ndb_configs"

. "$path/FINISH.sh"


1) get the Sakila database
2) change all occurrence of INNODB to PBXT
3) load the database
4) drop it

drop schema sakila;
ERROR 1217 (23000): Cannot delete or update a parent row: a foreign key
constraint fails

There was another occurrence of this bug, where PBXT reacted like Falcon
did in an old bug report of mine:

It occurred only once, using the employees test database, but the behavior
is similar. When attemting to drop the database, I got:
ERROR 1051 (42S02) at line 25: Unknown table

If I manage to reproduce the steps to get to this situation, I will let you



Giuseppe Maxia, MySQL Community Team Lead
Sun Microsystems, www.mysql.com

Related branches

I can confirm both cases - FK error and "unknown table"

Changed in pbxt:
assignee: nobody → Vladimir Kolesnikov (vkolesnikov)
status: New → Confirmed
Changed in pbxt:
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers