In article [EMAIL PROTECTED],
Kevin Cowley [EMAIL PROTECTED] writes:
If I knew why I wouldn't be asking. Now by our reconing the key of the
fields is 343 bytes, encoding in UTF8 makes that key 343 bytes Not 1000
since under utf8 each character is encode in 8 bits.
What makes you think so?
-Original Message-
From: Harald Fuchs [mailto:[EMAIL PROTECTED]
Sent: 30 September 2004 12:16
To: [EMAIL PROTECTED]
Subject: Re: Indexing problem with UTF8 in 4.1.4?
In article
[EMAIL PROTECTED],
Kevin Cowley [EMAIL PROTECTED] writes:
If I knew why I wouldn't be asking. Now
Kevin Cowley wrote:
Running 4.1.4 with a database that has a default encoding of UTF8
If we execute the following we get an error.
CREATE TABLE idxbe_resident (
urn INT UNSIGNED NOT NULL,
keyAddress_Part1 CHAR(5) BINARY NOT NULL,
dataPerson_Name CHAR(60),
dataAddress_Part1 CHAR(140),
Kevin Cowley
RD
Tel: 0118 902 9099 (direct line)
Email: [EMAIL PROTECTED]
Web: http://www.alchemetrics.co.uk
-Original Message-
From: gerald_clark [mailto:[EMAIL PROTECTED]
Sent: 29 September 2004 17:29
To: Kevin Cowley
Cc: [EMAIL PROTECTED]
Subject: Re: Indexing problem
