Re: Good structure for diversified data
Posted by: Rick James
Date: November 02, 2013 04:27PM

> or whether I could use a better table structure

Please show us your table structure. And please do it using SHOW CREATE TABLE.

First of all, be sure everything (client, tables, server, etc) is using utf8 (or utf8mb4). The collation can be utf8_bin, utf8_general_ci, or utf8_unicode_ci -- that depends on issues not yet discussed.

One table would be something like:
CREATE TABLE PhraseXlate (
phrase_id ... NOT NULL,
phrase TEXT NOT NULL,
PRIMARY KEY(phrase_id)
);

Pick the datatype for phrase_id based on what works out well elsewhere -- perhaps an INT, perhaps the phrase in, say, English. Then use phrase_id in any other tables that need it.

This table would have 30 rows for each phrase_id (assuming you have translated it into 30 languages).

> 30 fields for a short phrase, 30 fields for a description, 30 fields for editor lock, 30 fields for comments etc

Quite possibly all of those use phrase_id. And PhraseXlate is oblivious to which rows are holding "short phrases" versus "comments", etc.

> Module_Stamm

I don't know what this is; seems like a complication.

Options: ReplyQuote


Subject
Written By
Posted
Re: Good structure for diversified data
November 02, 2013 04:27PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.