List:General Discussion« Previous MessageNext Message »
From:Michael Widenius Date:August 29 1999 1:43am
Subject:Re: Extended ASCII in INSERT statements.
View as plain text  
>>>>> "Steven" == Steven Fletcher <flec@stripped> writes:

Steven> On Sun, 29 Aug 1999 01:35:14 +0300 (EEST), you wrote:
>> same. If you don't want this, declare your column as 'BINARY' or

Steven> Excellent, thanks for the prompt reply.

Steven> Adding the binary attribute has certainly fixed the insert statement,
Steven> but now has had the unfortunate side effect of removing the
Steven> case-insensitivity of the chan column that I was relying on previously
Steven> for easy searches.

Steven> Is it at all possible to keep both functions?

Only by defining a character set that doesn't map 'é' to 'e'.

You can of course also do something like:

SELECT ... WHERE CASEUP(a) LIKE CASEUP("%asdfsd%")

Regards,
Monty
Thread
Extended ASCII in INSERT statements.(Steven Fletcher)28 Aug
  • Extended ASCII in INSERT statements.Michael Widenius29 Aug
    • Re: Extended ASCII in INSERT statements.(Steven Fletcher)29 Aug
      • Re: Extended ASCII in INSERT statements.Michael Widenius29 Aug
  • Re: Extended ASCII in INSERT statements.Jim Faucette29 Aug