]> git.koha-community.org Git - koha.git/commit
Bug 18173: Remove DB field issues.return
authorJonathan Druart <jonathan.druart@bugs.koha-community.org>
Mon, 27 Feb 2017 09:41:55 +0000 (09:41 +0000)
committerKyle M Hall <kyle@bywatersolutions.com>
Fri, 31 Mar 2017 11:21:56 +0000 (11:21 +0000)
commit9236efdb5727189478f317ab4d1c61fc8556194d
treeda51e529faa85014f329aeb5f109b5233d11199c
parent4bd8b751e396eca594606b988de1fa5dbf3fd73f
Bug 18173: Remove DB field issues.return

The DB field issues.return has never really been used apparently.
I found the first occurrence of this field in
commit eac3a7b19a8aa7cda34aac396f5093c213a4aa5a
CommitDate: Mon Mar 12 22:43:47 2001 +0000
    Database definition file, checked into cvs to make keeping database
    current easier

Since I did not find any use of this field.
I guess it can be removed safely.

There is no proper test plan here. Just make sure this field has never
been used.

Signed-off-by: Magnus Enger <magnus@libriotech.no>
I have not found any use of issues.return or old_issues.return. In
all my live instances the column is always NULL. Issuing and returning
seems to work as expected after the columns have been removed.

Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com>
installer/data/mysql/atomicupdate/bug_18173.perl [new file with mode: 0644]
installer/data/mysql/kohastructure.sql