2012/01/16 19:57 -0800, Haluk Karamete
MSSQL can be configured to work in either mode. Isn't such a thing for mySQL?
For most of the time, I would not care about case-sensitivity. So I
won't mind configuring the entire mysql operation to be case
insensitive once and for all?
In M
In the last episode (Jan 16), Haluk Karamete said:
> How do I do case insensitive searches and replace operations? Is there an
> easy way to do this? Like some sort of a server level setting telling
> mySQL to ignore case for once and for all?
For searches (i.e. comparisons in the WHERE clause),
Thank you for your reply... But isn't "like" very very slow in
comparison to a none-like straight search?
Isn't it an overkill for a case sensitivity issue?
It appears to me that like has its own usage arena and case
sensitivity issue won't just justify the use of it...
MSSQL can be configured to
use LIKE
On Jan 17, 2012, at 10:36 AM, Haluk Karamete wrote:
> How do I do case insensitive searches and replace operations?
> Is there an easy way to do this? Like some sort of a server level
> setting telling mySQL to ignore case for once and for all?
>
> --
> MySQL General Mailing List
> F
How do I do case insensitive searches and replace operations?
Is there an easy way to do this? Like some sort of a server level
setting telling mySQL to ignore case for once and for all?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.
New "binary" character set should appear in next release.
It provides case-sensitive comparisons. It even doesn't
require recompiling mysqld, you need just to put binary.conf
file into /share directory of mysql installation, then restart
mysqld with "--default-character-set=binary" argument.
If yo
Giuseppe Maxia <[EMAIL PROTECTED]> responded:
> The workaround is to use the attribute BINARY for your field
> create table test (myfield varchar(80) BINARY not null, UNIQUE KEY myfield);
> This way, the index is case sensitive.
>
> Unfortunately, this feature was introduced in MySQL 3.23, so y
12/11/2001 17:34:07, Fulko Hew <[EMAIL PROTECTED]> wrote:
>
>I am using mySQL 3.22.4a-beta
>yes, I know its old :-(
>
>I have just stumbled across a problem with how it
>treats 'uniqueness' in table contents.
>
>I have a table with a column defined as:
>
> create table test (name varchar(80) not
Bill Adams <[EMAIL PROTECTED]> replied:
> Fulko Hew wrote:
>
> > I am using mySQL 3.22.4a-beta
> > yes, I know its old :-(
> >
> > I have just stumbled across a problem with how it
> > treats 'uniqueness' in table contents.
> >
> > I have a table with a column defined as:
> >
> > create table
> If you create your columns with the 'binary' parm (look in the manual),
> then all the comparisons will be case-sensitive.
> >Can anyone either point out what I am doing wrong, or a workaround?
>
database, mysql, table
-
Fulko Hew wrote:
> I am using mySQL 3.22.4a-beta
> yes, I know its old :-(
>
> I have just stumbled across a problem with how it
> treats 'uniqueness' in table contents.
>
> I have a table with a column defined as:
>
> create table test (name varchar(80) not null);
> alter table test ADD UNIQ
I am using mySQL 3.22.4a-beta
yes, I know its old :-(
I have just stumbled across a problem with how it
treats 'uniqueness' in table contents.
I have a table with a column defined as:
create table test (name varchar(80) not null);
alter table test ADD UNIQUE (name), ADD INDEX (name);
When
12 matches
Mail list logo
