Backport r18516: Ensure call numbers are returned to the holdings editor in ascending...
authordbs <dbs@dcc99617-32d9-48b4-a31d-7c20da2025e4>
Thu, 28 Oct 2010 15:10:53 +0000 (15:10 +0000)
committerdbs <dbs@dcc99617-32d9-48b4-a31d-7c20da2025e4>
Thu, 28 Oct 2010 15:10:53 +0000 (15:10 +0000)
commit4759037b1de3be1fce398a6eaefd16230b50ff2a
tree0c696bfb9d7c466e109ccfa75429d4bb3cf7d180
parent2dc2b3c30941c119d1839f50c0af5d91775e5fe7
Backport r18516: Ensure call numbers are returned to the holdings editor in ascending sorted order

James Fournie in https://bugs.launchpad.net/evergreen/+bug/635121 reported
that call numbers were being displayed in the order that they had been
added to the database, rather than in sorted call number label order.

Although I have been unable to reproduce this problem on two different
test systems, the patch he provided for 1.6.1 (which fixes the problem on their
test system) shouldn't hurt other systems.

For sortkey-aware branches, I modified James' patch to take advantage of the
asset.call_number.label_sortkey column and the oils_text_as_bytea() function.

git-svn-id: svn://svn.open-ils.org/ILS/branches/rel_2_0@18518 dcc99617-32d9-48b4-a31d-7c20da2025e4
Open-ILS/src/perlmods/OpenILS/Application/Cat.pm