modware-import error: stockcollection table does not exist

[biodavidjm]

Running modware-import dictyplasmid2chado -c configuration.yaml throws the following error:

DBIx::Class::ResultSet::count(): DBI Exception: DBD::Oracle::db prepare_cached failed: ORA-00942: table or view does not exist (DBD ERROR: error possibly near <*> indicator at char 23 in 'SELECT COUNT( * ) FROM <*>stockcollection me WHERE ( name = :p1 ) ') [for Statement "SELECT COUNT( * ) FROM stockcollection me WHERE ( name = ? ) "] at /Library/Perl/5.16/Modware/Role/Stock/Import/DataStash.pm line 370
DBIx::Class::Carp::__ANON__(): A DBIx::Class::Storage::TxnScopeGuard went out of scope without explicit commit or error. Rolling back. at /System/Library/Perl/Extras/5.16/DBIx/Class/Storage/TxnScopeGuard.pm line 132

Pre-diagnosis It seems that the stockcollection table that Modware/Role/Stock/Import/DataStash.pm should create, it is not working. This is the subroutine involved in the incident:

sub create_stockcollection {
    my ( $self, $name, $type_id ) = @_;
    my $stockcollection_rs
        = $self->schema->resultset('Stock::Stockcollection')->create(
        {   type_id    => $type_id,
            name       => $name,
            uniquename => $self->utils->nextval( 'stockcollection', 'DSC' )
        }
        );
    if ($stockcollection_rs) {
        return $stockcollection_rs->stockcollection_id;
    }
    return;
}

[cybersiddhu]

The assumption for test based software development is if the unit test passes then you are done with your code. It should work with real data. If it is not then fix the unit test or add more condition to it.

I would try to follow the steps

• Does this applications runner have a unit test ?
• If so does it pass ? If passes then it is done, there is nothing to be done.
• If it does not have unit tests then write one.

So, my first strong suggestion is

• Create your own git branch using gitflow model.
• Decide which code you want to work on.
• If you have come this far, try to run the script. If it goes through, then understand what it does. Remember every software has dependencies, our needs a database.
• If it fails go back to above testing steps.