Comment 3 for bug 800846

Got the following in JavaScript console while running with the attached patch on a system based on master with 271 config.circ_matrix_matchpoint entries:

Error: uncaught exception: {"hash":{"threadTrace":0,"type":"REQUEST","payload":{"hash":{"method":"open-ils.pcrud.search.ccmm","params":["be26267bc61cc35cd018d4b4e3459537",{"id":{"!=":null}},{"order_by":{"ccmm":"circ_modifier"},"limit":9000000000000000}]},"_encodehash":true,"method":null,"params":null,"serialize":null},"locale":"en-US"},"_encodehash":true,"threadTrace":null,"type":null,"payload":null,"locale":null,"serialize":null}

and the policy editor never populates, of course.

pen-ils.pcrud 2011-06-22 16:45:34 [INFO:5423:osrf_application.c:1040:130877528654856] CALL: open-ils.pcrud open-ils.pcrud.search.ccmm "be26267bc61cc35cd018d4b4e3459537",{"id":{"!=":null}},{"order_by":{"ccmm":"circ_modifier"},"limit":9000000000000000}
open-ils.pcrud 2011-06-22 16:45:34 [ERR :5423:oils_sql.c:5512:130877528654856] open-ils.pcrud: Error retrieving config::circ_matrix_matchpoint with query [SELECT "ccmm".id, "ccmm".is_renewal, "ccmm".active, "ccmm".org_unit, "ccmm".copy_circ_lib, "ccmm".copy_owning_lib, "ccmm".user_home_ou, "ccmm".grp, "ccmm".circ_modifier, "ccmm".marc_type, "ccmm".marc_form, "ccmm".marc_bib_level, "ccmm".marc_vr_format, "ccmm".ref_flag, "ccmm".juvenile_flag, "ccmm".usr_age_lower_bound, "ccmm".usr_age_upper_bound, "ccmm".item_age, "ccmm".circulate, "ccmm".duration_rule, "ccmm".recurring_fine_rule, "ccmm".max_fine_rule, "ccmm".hard_due_date, "ccmm".renewals, "ccmm".grace_period, "ccmm".script_test, "ccmm".total_copy_hold_ratio, "ccmm".available_copy_hold_ratio FROM config.circ_matrix_matchpoint AS "ccmm" WHERE "ccmm".id IS NOT NULL ORDER BY circ_modifier LIMIT -889552896;]: 0 ERROR: LIMIT must not be negative

Got the above in osrfsys.log.

It looks like the limit is going negative on my system. However, I don't see where in your patch the limit is being set. Rather bizarre.

On an unpatched system, running code that is otherwise identical to my dev server, I don't get the above error.

I applied the patch rather than merge your git branch because I'm trying to keep my dev environment as close to what we're running in production as possible at the moment. I might merge the branch and give that a try later to see if the behavior continues.