tripal_chado_prepare_chado fails if items already prepared
risharde opened this issue · 0 comments
Hi @laceysanderson , I thought I would drop this in here because it's not a bug per say but rather an issue I'm coming across during testing the prepare part after installing chado. Basically the entire prepare fails once this stuff exists and I was wondering if we could do anything about this (since prepare is technically to be run on a new instance of chado - this would break functionality for someone adding a secondary chado as there seems to be dependency on the tripal tables). I'm tagging @spficklin as well on what he also thinks we should or should not do? This also causes my code to prepare loader tables to not be reached so I wonder if there's a compromise we can make somewhere or not
Running as user 'admin'
2022-01-18 21:47:09: Job ID 10.
2022-01-18 21:47:09: Calling: tripal_chado_prepare_chado(chado)
Setting Schema to "chado".
Loading ontologies...
[warning] Creating default object from empty value TripalTermStorageChado.php:272
[warning] Creating default object from empty value TripalTermStorageChado.php:246
[warning] Creating default object from empty value TripalTermStorageChado.php:272
[warning] Creating default object from empty value TripalTermStorageChado.php:246
[warning] Creating default object from empty value TripalTermStorageChado.php:272
[warning] Creating default object from empty value TripalTermStorageChado.php:246
[warning] Creating default object from empty value TripalTermStorageChado.php:272
[warning] Creating default object from empty value TripalTermStorageChado.php:272
[warning] Creating default object from empty value TripalTermStorageChado.php:246
[warning] Creating default object from empty value TripalTermStorageChado.php:272
[warning] Creating default object from empty value TripalTermStorageChado.php:246
Creating default content types...
[warning] Creating default object from empty value TripalTermStorageChado.php:298
[error] Message: Job execution failed: 'tripal_entity_type' entity with ID 'bio_data_1'
already exists.