Feature #11404: Add command line script option to delete all descriptions for the selected archival institution - Access to Memory (AtoM) - Artefactual Projects

Feature #11404

Add command line script option to delete all descriptions for the selected archival institution

Added by Mike Gale almost 5 years ago. Updated over 4 years ago.

Status:

Verified

Start date:

07/11/2017

Priority:

Medium

Due date:

Assignee:

Dan Gillean

% Done:

Category:

CLI tools

Estimated time:

9.00 hours

Target version:

Release 2.4.0

Google Code Legacy ID:

Tested version:

History

#2 Updated by Mike Gale almost 5 years ago

Status changed from New to QA/Review

merged mainline qa/2.4.x 91584d8

#3 Updated by Dan Gillean almost 5 years ago

Category set to CLI tools
Target version set to Release 2.4.0
Sponsored changed from No to Yes
Requires documentation set to Yes

#4 Updated by Dan Gillean almost 5 years ago

Status changed from QA/Review to Feedback
Assignee changed from Dan Gillean to Mike Gale

I tried this, and got an error.

to reproduce

Create a new repo - "Test repo"
Create several new hierarchical descriptions (e.g. collection with children), associated with test repo
Run the task:

php symfony tools:delete-description --repository test-repo

Resulting error

Task fails to execute. The following error was returned:

Unable to execute DELETE statement. [wrapped: SQLSTATE[23000]: Integrity constraint violation: 1451 Cannot delete or update a parent row: a foreign key
 constraint fails (`atom`.`information_object`, CONSTRAINT `information_object_FK_5` FOREIGN KEY (`parent_id`) REFERENCES `information_object` (`id`))]

#5 Updated by Mike Gale almost 5 years ago

Assignee changed from Mike Gale to Dan Gillean

Hi Dan, did you get a chance to recreate this? It worked on my end, and I suspected it's possibly a cache issue. If you can reproduce, please provide a dump.

#6 Updated by Dan Gillean almost 5 years ago

Assignee changed from Dan Gillean to Mike Gale

Purged my site, dropped and reloaded the db, did a sql upgrade, restarted services, and reloaded the demo data. Still getting the same error. I've sent you an email with a sqldump attached.