Hi there,
i'm kinda stuck on a problem with an EE here. It's a shop which has
about 14 languages, therefore it has all translateable fields 14 times.
in oxarticles, thats a total of 206 (sic!) columns.
This blows up the row limit of 8000 bytes of innodb, if you want to add
another row to this table and you get "got error 139 from storage
engine". Some other developer seems to have already converted the
variant fields to text fields, instead of varchars. if you convert this
fields back to varchar, you get this:
#1118 - Row size too large. The maximum row size for the used table
type, not counting BLOBs, is 65535. You have to change some columns to
TEXT or BLOBs
Because of this, you aren't able to add one more column to this table,
which makes it incredibly hard to maintain this shop and do some updates
or install modules. i surely will find a solution for this, but it's an
unecessary "stone" in my way to update this shop.
I think the denormalized database layout should be seriously revamped at
least for multilanguage fields, and the step has to be to a more
normalized table layout for this purpose.
Any ideas for a new language management? Maybe we can figure out some
solution for oxid in general, together.
_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general
