Re: [pgsql-advocacy] interesting PHP/MySQL thread
От | nolan@celery.tssi.com |
---|---|
Тема | Re: [pgsql-advocacy] interesting PHP/MySQL thread |
Дата | |
Msg-id | 20030623053352.1457.qmail@celery.tssi.com обсуждение исходный текст |
Ответ на | Re: [pgsql-advocacy] interesting PHP/MySQL thread (The Hermit Hacker <scrappy@postgresql.org>) |
Ответы |
Re: [pgsql-advocacy] interesting PHP/MySQL thread
Re: [pgsql-advocacy] interesting PHP/MySQL thread Re: [pgsql-advocacy] interesting PHP/MySQL thread Re: [pgsql-advocacy] interesting PHP/MySQL thread Re: [pgsql-advocacy] interesting PHP/MySQL thread Re: [pgsql-advocacy] interesting PHP/MySQL thread |
Список | pgsql-general |
> > Personally, if I want case insensitivity, I'll WRITE IT INTO THE CODE, > > but I can see how some people might think that 'NOLAN', 'Nolan' and > > 'nolan' should be considered as the same data. > > Oh, you mean like "SELECT * FROM table WHERE field ~* 'nolan';"? No, I mean as in "SELECT * FROM table WHERE field = 'nolan';" That will match values with any combination of upper and lower case letters that fold to 'nolan': 'Nolan', 'NOLAN', etc. Also, unlike PostgreSQL (at least in 7.3), if you define an index on the column, mysql appears to use it for LIKE queries. "SELECT * FROM table WHERE field LIKE 'nolan%';" is very fast in mysql but not in 7.3, and even non-anchored LIKE searches in mysql appear to be using the index. "SELECT * FROM table WHERE field LIKE '%nolan%';" executes considerably faster with an index on field than without one. -- Mike Nolan
В списке pgsql-general по дате отправления: