Bug 2898 – With MySQL foreign key constraint fails during rescan.

Bug 2898 - With MySQL foreign key constraint fails during rescan.

Summary:

With MySQL foreign key constraint fails during rescan.

Status:	RESOLVED DUPLICATE of bug 2850

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Database
Version:	6.2.1
Platform:	Other Linux (other)

Importance:	P2 major (vote)
Target Milestone:	---
Assigned To:	Dan Sully

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2006-01-30 15:13 UTC by Robin Rainton
Modified:	2006-01-30 15:15 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Robin Rainton 2006-01-30 15:13:32 UTC

I'm using slimserver 6.2.1 with MySQL database backend.

When told to rescan the following error occurs:

Can't delete file://Yada.flac: DBD::mysql::st execute failed: Cannot delete or update a parent row: a foreign key constraint fails at /usr/local/slimserver/CPAN/DBIx/ContextualFetch.pm line 51.
 at /usr/local/slimserver/Slim/DataStores/DBI/DBIStore.pm line 652

This is a fatal error and causes slimserver to crash.

Emptying all tables by hand fixes this but has to be done in funny order to avoid foreign key problems.

Comment 1 KDF 2006-01-30 15:15:07 UTC

This is a dupe of 2850.  If you feel there is applicable information to add, please add comments to that bug report. thanks.

*** This bug has been marked as a duplicate of 2850 ***