https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35625 --- Comment #12 from Pedro Amorim <pedro.amorim@ptfs-europe.com> --- (In reply to Jonathan Druart from comment #11)
Then maybe you need 2 different DB tables.
One perl module (generic ticket) that will be inherited by the two specific ticket modules.
It's not a bad thing to have different DB tables when your objects are different. Then if you need repeatable fields, you create yet another table with 1-n relationship. It's... relational models and database normalization ;)
Yes but you're highlighting exactly why this approach is worth considering in the first place. Why re-implement anything that's already been implemented at the additional_fields level? We already have patron_custom_attributes and additional_fields, 2 implementations of what is essentially the same thing, but now need to be maintained and supported individually. This is exactly what we're aiming to prevent here: implement yet another redundant metadata table that needs to do something that's already implemented in Koha. -- You are receiving this mail because: You are watching all bug changes.