Summary: | Error in logic CheckBorrowerDebarred | ||
---|---|---|---|
Product: | Koha | Reporter: | Jorge de Cardenas <jdeca> |
Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
Status: | CLOSED INVALID | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | chris, fred.pierre, gmcharlt, katrin.fischer, kyle.m.hall |
Version: | 3.8 | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: |
Description
Jorge de Cardenas
2012-11-15 18:38:27 UTC
debarred is now a date field in the database (connected to the fines in days feature) - which version are you looking at? I believe this is a legacy data issue. New patrons are given a debarred date of 12-31-9999, debarred patrons are assigned a specific debarred date, while legacy patrons retain a [NULL] for debarred status in the borrowers table. Custom scripts will need to address these three possibilities. (In reply to comment #1) > debarred is now a date field in the database (connected to the fines in days > feature) - which version are you looking at? I have to systems running a test system which is 3.09.00.029 at a system I'm preparing to migrate our data into which is 3.09.00.059. On the .029 the database is still a tinyint for that field. It could have been that the database conversion failed. The .059 system has the correct datatype. |