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

            Bug ID: 18428
           Summary: Duplicate key error in old_reserves table.
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5 - low
         Component: Database
          Assignee: gmcha...@gmail.com
          Reporter: bar...@bywatersolutions.com
        QA Contact: testo...@bugs.koha-community.org

I'm not exactly sure how we got ourseleves into this situation, but one of our
libraries is getting the following error when trying to check in an item that
is on hold:

DBD::mysql::st execute failed: Duplicate entry '39' for key 'PRIMARY' [for
Statement "INSERT INTO `old_reserves` ( `biblionumber`, `borrowernumber`,
`branchcode`, `cancellationdate`, `expirationdate`, `found`, `itemnumber`,
`itemtype`, `lowestPriority`, `notificationdate`, `priority`, `reminderdate`,
`reserve_id`, `reservedate`, `reservenotes`, `suspend`, `suspend_until`,
`timestamp`, `waitingdate`) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
?, ?, ?, ?, ? )" with ParamValues: 0='11198', 1='693', 2='CFOT', 3=undef,
4=undef, 5='F', 6=undef, 7=undef, 8='0', 9=undef, 10=0, 11=undef, 12='39',
13='2017-04-13', 14='', 15='0', 16=undef, 17='2017-04-13 06:19:29', 18=undef]
at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1832.
DBIx::Class::Storage::DBI::_dbh_execute(): Duplicate entry '39' for key
'PRIMARY' at /usr/share/koha/lib/Koha/Object.pm line 120

This is analogous to bug 18242 for old_issues.

I wonder if we need to do the same thing for the deleted* tables.

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to