[Koha-bugs] [Bug 18086] overduerules table is lacking foreign key constraints

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18086

--- Comment #21 from Kyle M Hall <kyle at bywatersolutions.com> ---
(In reply to Katrin Fischer from comment #20)
> Hi Kyle,
> 
> working through this and it looks good overall until now. But the tests need
> to be updated as well I think:
> 
> $ prove t/db_dependent/Overdues.t 
> t/db_dependent/Overdues.t .. 1/17 {UNKNOWN}: DBI Exception: DBD::mysql::db
> do failed: Cannot add or update a child row: a foreign key constraint fails
> (`koha_kohadev`.`overduerules`, CONSTRAINT `fk_branchcode` FOREIGN KEY
> (`branchcode`) REFERENCES `branches` (`branchcode`) ON DELETE CASCADE ON
> UPDATE CASCADE) [for Statement "
>     INSERT INTO overduerules ( overduerules_id, branchcode, categorycode )
> VALUES
>     (1, 'CPL', 'PT'),
>     (2, 'CPL', 'YA'),
>     (3, '', 'PT'),
>     (4, '', 'YA')
> "]  at /usr/share/perl5/DBIx/Class/Schema.pm line 1118.
> 	DBIx::Class::Schema::throw_exception(Koha::Schema=HASH(0x5626c3608c58),
> "DBI Exception: DBD::mysql::db do failed: Cannot add or update"...) called
> at /usr/share/perl5/DBIx/Class/Storage.pm line 113
> 	DBIx::Class::Storage::throw_exception(DBIx::Class::Storage::DBI::
> mysql=HASH(0x5626c3e11be8), "DBI Exception: DBD::mysql::db do failed: Cannot
> add or update"...) called at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line
> 1501
> 	DBIx::Class::Storage::DBI::__ANON__("DBD::mysql::db do failed: Cannot add
> or update a child row: a"..., DBI::db=HASH(0x5626c44f6520), undef) called at
> t/db_dependent/Overdues.t line 33
> 
> # Looks like your test exited with 255 just after 3.
> t/db_dependent/Overdues.t .. Dubious, test returned 255 (wstat 65280, 0xff00)
> Failed 14/17 subtests 
> 
> Test Summary Report
> -------------------
> t/db_dependent/Overdues.t (Wstat: 65280 Tests: 3 Failed: 0)
>   Non-zero exit status: 255
>   Parse errors: Bad plan.  You planned 17 tests but ran 3.

I'm unable to recreate your error. Are you using a fresh database?

-- 
You are receiving this mail because:
You are watching all bug changes.