Hi Ron,
What if the 7 «Custom» fields were set to text, instead of varchar 255, in the database? You never know until you ask...
Thanks again for your great work.
jv

Comments

rjerome’s picture

rjerome commented

I'm guessing you need a bigger field?

Actually I was toying with restructuring the database such that data would no longer be stored in rows in the biblio table, but rather there would be a new table called biblio_data with a few columns (vid, field_type, value). value would them be "text" for all fields.

The downside to this is you couldn't go into the database a see all the values for a given entry in one row, the upside is it is much more efficient use of storage.

jeromev’s picture

jeromev commented

Personally, I would not see any problem concerning the downside you mention, if we can gain efficiency. I'm just wondering about the upgrade process to move all the data...
jv

rjerome’s picture

rjerome commented

Yes, well the devil is in the details... But seriously, I don't see that as a major problem, it's just a matter of parsing through the existing records and re-saving them in the new format, throw in a little validation, then clean out the original table. This of course will all be done by the update process, so (hopefully) the user will never know it happened.

bekasu’s picture

bekasu commented
Status: Active » Closed (fixed)

Marking issue closed.