you not ADD Binary, you need to "remove" BINARY ... ;-)
Sorry, I misunderstood.
convert the string to latin1 or utf8 o.s.s.
"LOWER() (and UPPER()) are ineffective when applied to binary strings
(BINARY, VARBINARY, BLOB). To perform lettercase conversion, convert the
string to a non-binary s
> -Original Message-
> From: Jesse [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 12, 2008 1:40 PM
> To: Martijn Tonies; MySQL List
> Subject: Re: Function Still Not Working
>
> > Any difference in default collation?
>
> Not sure what that is. I'm
does it work outside the function?
Yes, If I run:
select CONCAT(UPPER(SUBSTRING('JESSE',1,1)),LOWER(SUBSTRING('JESSE',2)));
replacing cInput with 'JESSE', it returns "Jesse" as it should.
did you tried SUBSTRING(cInput, 2)?
Tried replacing SUBSTRING(cInput FROM 2) with SUBSTRING(cInput, 2)
Any difference in default collation?
Not sure what that is. I'm using a visual tool (EMS) to create my function,
and it doesn't offer that option. I could update it using the command
prompt, however. I may try that later.
--
MySQL General Mailing List
For list archives: http://lists.mys
I am curious about that, as well. It brings to mind a discussion that
happened on this list last week (I believe) about case
sensitive/insensitive use of LIKE. I believe the synopsis was that
tables are either created as case-insensitive, or the search needs to be
specified as case sensitive (with
> -Original Message-
> From: Martijn Tonies [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 12, 2008 6:23 AM
> To: MySQL List
> Subject: Re: Function Still Not Working
>
> Hey,
>
> > Sorry for posting this again, but I got only one response last time,
&g
Jesse schrieb:
Sorry for posting this again, but I got only one response last time, and
I'm still having the problem. I spent HOURS the other day manually
going through the data and Properizing these things by hand. I don't
want to do that again if I can avoid it. If anyone has any clues on
Hey,
> Sorry for posting this again, but I got only one response last time, and
I'm
> still having the problem. I spent HOURS the other day manually going
> through the data and Properizing these things by hand. I don't want to do
> that again if I can avoid it. If anyone has any clues on this o
Sorry for posting this again, but I got only one response last time, and I'm
still having the problem. I spent HOURS the other day manually going
through the data and Properizing these things by hand. I don't want to do
that again if I can avoid it. If anyone has any clues on this one, I would
