Since the message_id and app_name are part of the language independence,
why not just restrict them to the latin1 character set so they continue
to use one byte per character? A Chinese (for example) message_id seems
a little too flexible to me... leave the UTF character sets for fields
likely to have human readable (rather than developer readable, grin) text.
On 2006 04 22 11:01, Sigurd Nes wrote:
That would restrict the installation to only one language.
(this is only tested on windows/MySQL 5.0.18 - I think pre 4.1 - one
cannot specify utf8 (utf8_swedish_ci) as collation)
Regards
Sigurd
Dave Hall wrote:
We should change the pk to be message_id, app_name imo
Cheers
Dave
On Fri, 2006-04-21 at 18:14 +0200, Sigurd Nes wrote:
Problem:
The PRIMARY KEY ( message_id, app_name, lang ) of table phpgw_lang
is to long (max key length is 1000 bytes) when creating database as
utf8 with Mysql.
regards
Sigurd
_______________________________________________
Phpgroupware-developers mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/phpgroupware-developers
_______________________________________________
Phpgroupware-developers mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/phpgroupware-developers
_______________________________________________
Phpgroupware-developers mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/phpgroupware-developers