https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24190
--- Comment #19 from Andrew Isherwood <[email protected]> --- Hi Jonathan - After creating the patches to use JSON rather than zero padded strings, I remembered the reason I went for zero padded strings rather than another format. Since the content of the logged data needs to be used in SQL reports, I need it to be in a format that can be parsed using SQL. JSON is the obvious choice, however JSON support doesn't exist on the older versions of MySQL that Koha supports (e.g. 5.5), so that is not a viable option. The only method I could come up with for storing arbitrary data was in padded strings, then using the SUBSTRING operator to extract the data in a report. > And why 10? rrp_tax_excluded is decimal(28,6) for instance OK, I'd not appreciated that. I can increase the padding to a much larger value if we're allowing values with precision of 28 to be stored... I wanted the padding to be sufficient, 10 seemed to be enough, but apparently not. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
