koha-bugs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Koha-bugs] [Bug 637] issuingbranch is NULL in issues and statistics


From: bugzilla-daemon
Subject: [Koha-bugs] [Bug 637] issuingbranch is NULL in issues and statistics
Date: 28 Oct 2003 18:09:33 -0000

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=637

address@hidden changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED



------- Additional Comments From address@hidden  2003-10-29 07:09 -------
I just ran some tests and yes, branchcode gets set with the value that the item
was issued from, it then gets set with the value it was returned to as well.
So you lose the value of where it was issued from upon return, well in the
issues table you do, its still in the statistics table

Now in the statistics table

| datetime            | branch | proccode | value  | type  | other | usercode |
itemnumber | itemtype | borrowernumber |
+---------------------+--------+----------+--------+-------+-------+----------+------------+----------+----------------+
| 2003-10-28 17:42:35 | L      | NULL     | 0.0000 | issue |       |          |
     22614 | F        |             0 |

The branch there is where it was issued from

------------+----------+----------------+
| datetime            | branch | proccode | value  | type   | other | usercode |
itemnumber | itemtype | borrowernumber |
+---------------------+--------+----------+--------+--------+-------+----------+------------+----------+----------------+
| 2003-10-28 17:37:08 | L      | NULL     | 0.0000 | return |       |          |
     44600 |          |             0 |

And here its where it was returned to.
We dont have the borrowernumber, but we can get that from the issues table if we
want.


Hope this helps?




------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]