[Koha-bugs] [Bug 24986] Maximum row size reached soon for borrowers and deletedborrowers

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24986

Martin Renvoize <martin.renvoize at ptfs-europe.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |martin.renvoize at ptfs-europe
                   |                            |.com
             Status|Needs Signoff               |Signed Off

--- Comment #11 from Martin Renvoize <martin.renvoize at ptfs-europe.com> ---
I think the patch proposed here is a good (and back portable) fix for the issue
in hand so I'm signing off.

However, I do think we should certainly split out addresses into their own
table and follow proper 3rd normal form for then.. but I think that should be
on it's own bug.. (actually.. i thought there was already a bug for that, but I
can't seem to find it).

As for using JSON.. I'm not sure what that would win us really.. I like JSON
fields and used them in a postgres based system a while ago.. but the querying
did end up considerably more complex in the end and I ended up converting some
fields back to additional tables and using JOIN queries instead for performance
and readability reasons (dbic isn't great with JSON queries yet either).. I'd
say for now at least.. we don't have any cases where the advantage of JSON
fields outweighs the cost.. yet..

-- 
You are receiving this mail because:
You are watching all bug changes.