Bug 6124 - In transferstoreceive.pl some biblios are empty.
Summary: In transferstoreceive.pl some biblios are empty.
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Julian Maurice
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-07 15:20 UTC by Julian Maurice
Modified: 2014-12-07 20:03 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Patch (1.20 KB, patch)
2011-04-07 15:24 UTC, Julian Maurice
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Julian Maurice 2011-04-07 15:20:47 UTC
Due to the fact that it is possible to have some lines in branchtransfers with an itemnumber that does not exists in table items.
With the coming patch in this case the line with no biblios will be omitted.
Comment 1 Julian Maurice 2011-04-07 15:24:36 UTC
Created attachment 3815 [details] [review]
Patch
Comment 2 MJ Ray (software.coop) 2011-06-16 01:00:11 UTC
How is it possible to have a line in branchtransfers with an itemnumber that does not exist in table items?

Would it be better to put the rest of the processing inside the if () { ... } rather than use a next short-circuit?  Should we alert the user to the problem?
Comment 3 Paul Poulain 2011-10-24 11:38:17 UTC
Updating Version : This ENH will be for Koha 3.8
Comment 4 Paul Poulain 2011-10-25 15:05:53 UTC
Bug versionned for master. entries will be made against rel_3_8 once the patch has been applied (see thread about that on koha-devel yesterday)
Comment 5 Ian Walls 2012-02-03 13:08:14 UTC
Reiterating MJ's question:  how is this possible?  Please provide steps for reproducing this issue, so it can be tested.
Comment 6 Owen Leonard 2012-03-09 15:26:36 UTC
I'm changing this to "in discussion" to move it out of the signoff queue while we wait to hear answers to the questions in comments.
Comment 7 Galen Charlton 2013-08-12 17:15:58 UTC
Setting to RESOLVED/INVALID -- it's been over a year since the question was posed, and the FK on branchtransfers.itemnumber should make the bug impossible unless the wrong storage engine was being used.