[Bug 18338] New: Replace varchar(16) with varchar(32) for cardnumber
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18338 Bug ID: 18338 Summary: Replace varchar(16) with varchar(32) for cardnumber Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt@gmail.com Reporter: martin.renvoize@ptfs-europe.com QA Contact: testopia@bugs.koha-community.org CC: hector.hecaxmmx@gmail.com, indradg@l2c2.co.in, jonathan.druart@bugs.koha-community.org, julian.maurice@biblibre.com, kyle@bywatersolutions.com, m.de.rooy@rijksmuseum.nl, mtj@kohaaloha.com, oleonard@myacpl.org, testopia@bugs.koha-community.org, tomascohen@gmail.com, veron@veron.ch Depends on: 15690 Bug #15690 makes it more explicit that cardnumber is limited at the database level to 16 characters, but it does not go any way towards increasing that field length for those using cardnumbers of greater lengths. I think we should increase the database field size from 16 characters to 32, giving us ample growing space for longer cardnumbers. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15690 [Bug 15690] Unconstrained CardnumberLength preference conflicts with table column limit of 16 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18338 Josef Moravec <josef.moravec@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |josef.moravec@gmail.com Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Josef Moravec <josef.moravec@gmail.com> --- *** This bug has been marked as a duplicate of bug 13178 *** -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org