https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17196
Martin Renvoize <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.renvoize@ptfs-europe | |.com --- Comment #33 from Martin Renvoize <[email protected]> --- So.. I'm in favour of this in general.. But.. I'm wondering about the wisdom of the schema a bit. I would settle on a serialisation format (JSON, XML) and abstract the inflation/deflation of it into the dbic class using InflateColumn and friends. This would allow us to take advantage of either postgres's jsonb store or mysql's in built xml handling consistently allowing those tools to be fully utilised in reports. Without doing so, would mean reports would end up much more limited. So, I would ditch the 'format' field, fix the serialisation format in the metadata field and use dbic to inflate into perl data-structures consistently. We could still happily bind to the 'marcflavour' field to build objects of different types from the inflated perl structures (though I would change marcflavour to just flavour in case we want to support non-marc later ;) Just my two pence. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://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/
