Not a unicode one that I know of, converting it to latin1 for the grouping
works for that particular use case, but I can't make any promises how it'd
work on your entire set which may hold any unicode character, a lot of
which cannot be converted to latin1:
mysql SET NAMES utf8;
Query OK, 0 rows
Thanks for that answer. It squares with my solution: have an additional
column that has the lower case values of the case sensitive unicode
setting.
Martin Mueller
Professor emeritus of English and Classics
Northwestern University
On 11/25/14 6:48 AM, Rik r...@grib.nl wrote:
Not a unicode
Is there a unicode setting on mysql that is case insensitive but
diacritics sensitive? Given 'Ete', 'été', 'ete' a group by routine for
such a setting would return two values: 'été', 'ete'. I couldn't find
it, but I may not have known where to look.
Martin Mueller
Professor emeritus
sec)
I want it to give me data as
name cost
A 6700
B 12000
C NULL
But my query is not working -
MariaDB [tutorial] select name, CASE WHEN ISNULL(DISTINCT sum) THEN sum(cost)
ELSE NULL END AS cost_sum
- from prices group by name;
ERROR 1064 (42000): You have
| NULL |
++--+--+
6 rows in set (0.00 sec)
I want it to give me data as
name cost
A 6700
B 12000
C NULL
But my query is not working -
MariaDB [tutorial] select name, CASE WHEN ISNULL(DISTINCT sum) THEN
sum(cost)
ELSE NULL END
On Saturday, July 19, 2014 02:56:24 PM Reindl Harald wrote:
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual
that corresponds to your MariaDB server version for the right syntax to
use
near 'DISTINCT sum) THEN sum(cost) ELSE NULL END AS cost_sum
from prices
- Original Message -
From: Reindl Harald h.rei...@thelounge.net
Subject: Re: Case sensitivity
ALTER TABLE `my_table` DEFAULT CHARACTER SET latin1 COLLATE
latin1_general_ci;
Purely from memory, doesn't that change the table but add the old setting to
individual text columns?
I
On 05/21/2014 08:14 AM, Johan De Meersman wrote:
ALTER TABLE `my_table` DEFAULT CHARACTER SET latin1 COLLATE
latin1_general_ci;
Purely from memory, doesn't that change the table but add the old setting to
individual text columns?
right, the above will only change the default for new
Am 21.05.2014 10:50, schrieb Hartmut Holzgraefe:
On 05/21/2014 08:14 AM, Johan De Meersman wrote:
ALTER TABLE `my_table` DEFAULT CHARACTER SET latin1 COLLATE
latin1_general_ci;
Purely from memory, doesn't that change the table but add the old setting to
individual text columns?
right,
On Wed, May 21, 2014 at 4:50 AM, Hartmut Holzgraefe hart...@skysql.com wrote:
On 05/21/2014 08:14 AM, Johan De Meersman wrote:
ALTER TABLE `my_table` DEFAULT CHARACTER SET latin1 COLLATE
latin1_general_ci;
Purely from memory, doesn't that change the table but add the old setting to
server is case sensitive as you would expect, but the
5.0.77 is not. How can I make the 5.0.77 server case sensitive?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
|
+--+--+
2 rows in set (0.00 sec)
Yet the 5.5.25a server is case sensitive as you would expect, but the
5.0.77 is not. How can I make the 5.0.77 server case sensitive?
and what collation have your tables and databases?
what collation is the client *really* using?
set
On 05/20/2014 03:26 PM, Larry Martell wrote:
Yet the 5.5.25a server is case sensitive as you would expect, but the
5.0.77 is not. How can I make the 5.0.77 server case sensitive?
please provide the output of
SHOW VARIABLES LIKE 'character_set_%';
and
SHOW VARIABLES LIKE 'collation_
On Tue, May 20, 2014 at 9:38 AM, Hartmut Holzgraefe hart...@skysql.com wrote:
On 05/20/2014 03:26 PM, Larry Martell wrote:
Yet the 5.5.25a server is case sensitive as you would expect, but the
5.0.77 is not. How can I make the 5.0.77 server case sensitive?
please provide the output
PnLDetail;
+-+
| pnlCurrency |
+-+
| USD |
+-+
1 row in set (0.01 sec)
Both have the same data in them.
ok, in this case the interesting piece of information
would be the SHOW CREATE TABLE pnlCurrency; output
from both
rows in set (0.00 sec)
5.0 server:
mysql select distinct(pnlCurrency) from PnLDetail;
+-+
| pnlCurrency |
+-+
| USD |
+-+
1 row in set (0.01 sec)
Both have the same data in them.
ok, in this case the interesting piece of information
would
Am 21.05.2014 00:48, schrieb Larry Martell:
ok, in this case the interesting piece of information
would be the SHOW CREATE TABLE pnlCurrency; output
from both.
As the collation_database variables differ between the
two servers (utf8_bin vs. latin1_swedish_ci) I assume
that the same
It is my impression that when their functions are equivalent, IF takes more
time than CASE. Comment?
Do they always evaluate all their arguments?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
As a Rule of Thumb, function evaluation time is not significant to the overall
time for running a query. (I see IF and CASE as 'functions' for this
discussion.)
Do you have evidence that says that IF is slower? Perhaps using BENCHMARK()?
-Original Message-
From: h...@tbbs.net
2013/02/05 17:06 +, Rick James
As a Rule of Thumb, function evaluation time is not significant to the overall
time for running a query. (I see IF and CASE as 'functions' for this
discussion.)
Do you have evidence that says that IF is slower? Perhaps using BENCHMARK()?
Not BENCHMARK: I
it spreads!
In all seriousness, though, that's a pretty useful explanation. I've never run
into the case sensitivity in configfiles because I'm a lazy bugger, but I never
realized they were just turned into so much commandline options.
Thanks for that.
--
Linux Bier Wanderung 2012, now also
Yes, the missing piece of the puzzle is that configuration files are
turned into command line arguments internally. Programs will parse
configuration files and place them at the beginning of the array for
command line arguments. They are made case sensitive because they are
turned into command
line arguments internally. Programs will parse
configuration files and place them at the beginning of the array for
command line arguments. They are made case sensitive because they are
turned into command line arguments. So the basic process is read all
the configuration files in order
Anger and OS religious arguments the real answer is that is just how
the option parsing code works. It doesn't always have to make sense.
There are short and long args to programs. For example on the mysql
client there is --port or -P and --pasword or -p. The short options
have to be case
Dear Eric,
Thanks a lot for the explanation of argument directives! The concerns are
very considerate.
Actually, what I'm curious about is the configuration directives in the
configuration file, i.e., my.cnf. To my experience, MySQL is the very few
software who treats these directives in a case
Hi,
I'm just curious why MySQL parses its configuration directives (i.e., the
ones in my.cnf) in a case sensitive way?
For example, Having Port=3309, will receive unknown variable 'Port=3309.
I guess there must be some concern for this. Could anyone tell me why?
Thanks,
Tianyin
Am 18.11.2012 23:59, schrieb Tianyin Xu:
Hi,
I'm just curious why MySQL parses its configuration directives (i.e., the
ones in my.cnf) in a case sensitive way?
For example, Having Port=3309, will receive unknown variable 'Port=3309.
I guess there must be some concern for this. Could
Hi, Reindl,
On Sun, Nov 18, 2012 at 3:11 PM, Reindl Harald h.rei...@thelounge.netwrote:
Am 18.11.2012 23:59, schrieb Tianyin Xu:
Hi,
I'm just curious why MySQL parses its configuration directives (i.e., the
ones in my.cnf) in a case sensitive way?
For example, Having Port=3309
Am 19.11.2012 01:27, schrieb Tianyin Xu:
I'm not saying the file names but the configuration directives.
At least for most servers I have managed so far,
all the configuration directives are case insensitive. Examples? PostgreSQL,
Apache httpd, OpenLDAP, Squid, etc.
That's why I'm curious
Hi,
On Sun, Nov 18, 2012 at 4:35 PM, Reindl Harald h.rei...@thelounge.netwrote:
Am 19.11.2012 01:27, schrieb Tianyin Xu:
I'm not saying the file names but the configuration directives.
At least for most servers I have managed so far,
all the configuration directives are case insensitive
a configuration is
case-sensitive instead accept it and correct your fault
you are doing the wrong job
signature.asc
Description: OpenPGP digital signature
insecure
see all this CMS sytems out there writing hundrets of
warnings each request with error_reporting E_STRICT
while my whole source code runs clean i know who is right
really:
if you find it useful to complain why a configuration is
case-sensitive instead accept it and correct your fault
hundrets of
warnings each request with error_reporting E_STRICT
while my whole source code runs clean i know who is right
really:
if you find it useful to complain why a configuration is
case-sensitive instead accept it and correct your fault
you are doing the wrong job
--
MySQL General
I could suggest a number of ways around the if/else construct, such as
creating a subclass for the various servers with a uniform interface
and hiding the differences inside the class.
This, but I'd prefer using one of the already available abstractions for PHP:
- PDO: http://www.php.net/PDO
Please take a look at the following code and tell me if there is a way
around it.
if ($current_server_is_mysql):
while ($row = mysql_fetch_assoc($RS)) {
else:
while( $row = sqlsrv_fetch_array( $RS, SQLSRV_FETCH_ASSOC)){
endif:
Depending on the server I'm working with, I'd like to compile
-Original Message-
From: Haluk Karamete [mailto:halukkaram...@gmail.com]
Sent: Thursday, May 03, 2012 10:21 AM
To: MySQL
Subject: mixing and matching mysql mssql whileloop within an if case
Please take a look at the following code and tell me if there is a way
around
Sent from my iPhone
On May 3, 2012, at 1:02 PM, Haluk Karamete halukkaram...@gmail.com wrote:
Please take a look at the following code and tell me if there is a way
around it.
if ($current_server_is_mysql):
while ($row = mysql_fetch_assoc($RS)) {
else:
while( $row =
Haluk,
I could suggest a number of ways around the if/else construct, such as
creating a subclass for the various servers with a uniform interface
and hiding the differences inside the class. The actual error that you
showed is much simpler, however: you are mixing curly-brace style with
what I
I suppose an easier way is to have a getrow function, Something like
while ($row = getrow($RS) {
.
.
.
}
function getrow($RS)
{
if ($current_server_is_mysql)
{
return mysql_fetch_assoc($RS);
}
else
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 MySQL some
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
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
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
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
mysql select date_format(now(),'%m-%d%-%y
%h:%i:%s') AS time;
+---+
|
time
|
+---+
| 11-11-11 11:11:11 |
+---+
1 row in set (0.00 sec)
On 11/11/2011 16:29, Curtis Maurand wrote:
mysql select date_format(now(),'%m-%d%-%y
%h:%i:%s') AS time;
+---+
|
time
|
+---+
| 11-11-11 11:11:11 |
+---+
1 row in set (0.00 sec)
Actually, it should be select date_format(now(),'%y-%m%-%d
are!!! (for this case anyway)
-
Registered Office: 15 Stukeley Street, London WC2B 5LT, England.
Registered in England number 1421223
This message is for the designated recipient only and may contain privileged,
proprietary, or otherwise private information. If you have
Hi, Google isn't my friend :-(
How can I tell mySQL 5.0 to ignore the case of field names i.e. FullName
should also be able to be referenced as fullname,fullNAME etc ?
I'm running it on a linux box at home but my copy at work (running on
Windows 2000 server) has this by default - I certainly set
http://dev.mysql.com/doc/refman/5.0/en/case-sensitivity.html
You need to set the field format to a non binary one, and case
insensitive will be the default.
On Aug 27, 2009, at 2:57 PM, Adrian Aitken wrote:
Hi, Google isn't my friend :-(
How can I tell mySQL 5.0 to ignore the case of field
Adrian
- Original Message -
From: Scott Haneda
To: Adrian Aitken
Cc: mysql@lists.mysql.com
Sent: Thursday, August 27, 2009 11:04 PM
Subject: Re: Getting mySQL to ignore case sensitivity of field names
http://dev.mysql.com/doc/refman/5.0/en/case-sensitivity.html
You need to set the field
Oops, sorry about that. My understanding is this is OS dependent:
http://dev.mysql.com/doc/refman/5.0/en/identifier-case-sensitivity.html
You may be able to set lowercase tables names, but would always have
to use lowercase. I would just stick to entering in the correct case,
as the other
link seems to only talk about field values.
That should not happen. Column names are not case sensitive in MySQL.
http://dev.mysql.com/doc/refman/5.0/en/identifier-case-sensitivity.html:
Column, index, and stored routine names are not case sensitive on any
platform, nor are column aliases
How to Create a Test Case
http://forge.mysql.com/wiki/How_to_Create_a_Test_Case
This Thursday (April 2nd, 14:00 UTC), Patrick Crews will give a MySQL
University session on How to Create a Test Case. This is an updated
session of a talk we had in 2007, but this time it will be recorded
(slides
, configured
with MySQL. I found that some of the tests were failing, apparently because
of table name case-sensitivity issues. I was able to fix some of the code
references, but after that I hit other, probably for the same issue. The
tables were created with lower case names, but generated
Ubuntu 8.10.
I was experimenting with the Spring Petclinic sample application,
configured with MySQL. I found that some of the tests were failing,
apparently because of table name case-sensitivity issues. I was able to
fix some of the code references, but after that I hit other, probably
I tried something like this but it doesnt work. Thank you..
SELECT table_1.id FROM table_1
CASE
WHEN (table_1.pid 0)
THEN LEFT JOIN table_2 ON table_1.pid = table_2.id
WHEN (table_1.nid 0)
THEN LEFT JOIN table_3 ON table_1.nid = table_3.id
END
2009/2/24 Ali Deniz EREN ali.deniz.e
you are treating it as two different cases,
using data from table_2 or table_3. This is correct.
But rather than trying to decide on a case-by-case basis depending on
the values in table_1, you should fully separate them.
First, try to come up with a SELECT that will return all relevant data
from
table_1
id pid nid
---
1 60
2 05
table_2 (referer - pid)
id title body
---
1 title1 body_text1
2 title2 body_text2
3 title3 body_text3
4 title4 body_text4
5 title5 body_text5
6 title6 body_text6
7 title7
How can I use REGEXP case insensitive SQL QUERY
Ex: select * from table where a REGEXP 'abc' will match both 'abc' and 'ABC'
that in query browser, but that
doesn't prevent another thread to modify locked table.
--
View this message in context:
http://www.nabble.com/How-to-guarantee-an-integrity-in-this-case--tp17988300p17988300.html
Sent from the MySQL - General mailing list archive at Nabble.com.
--
MySQL General
Hi,
I want to do this:
[1] read a row from table table_1 with select
[2] change a row from [1] with update
[3] change another row in table table_1 with update
But queries [2] and [3] in the time of invoking, assume that row from
query
[1] wasn't changed.
Should I use LOCK TABLES? - I've
the permissions to 660 (with user as mysql)
restarted the mysql server.
I can see all the tables but when i fire following query
select * from table_name
i get the following error
*./new_db/table_name.frm not found*
**
**
can anybody help me in changing the table names to upper case
Thanks In Advance
case
when table names are in uppercase you have also write this in your queries:
select * from TABLE_NAME
or read:
http://dev.mysql.com/doc/refman/5.0/en/identifier-case-sensitivity.html
--
Sebastian Mendel
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
Could someone explain the logic of how case sensivity works on stored
procedure formal argument names?
Example:
CREATE PROCEDURE sp_Test ( IN col1 INT,
IN col2 INT )
BEGIN
INSERT INTO Table
SET COL1 = col1,
COL2 = col2;
END
We've found
Im trying to create one query here. I know why its failing because CASE can
not be used like this, but how could I ever do a query like this.
[CODE]
SELECT b.*
FROM bonus b
JOIN
CASE b.type
WHEN 'custom' THEN 'bonusCustom g'
WHEN 'pts' THEN 'bonusPts g
altendew wrote:
Im trying to create one query here. I know why its failing because CASE can
not be used like this, but how could I ever do a query like this.
[CODE]
SELECT b.*
FROM bonus b
JOIN
CASE b.type
WHEN 'custom' THEN 'bonusCustom g'
WHEN 'pts
What do you mean assemble the SQL in Code.
I am using MYSQL 4.1 and PHP.
Daniel Kasak wrote:
altendew wrote:
Im trying to create one query here. I know why its failing because CASE
can
not be used like this, but how could I ever do a query like this.
[CODE]
SELECT b.*
FROM bonus b
altendew wrote:
What do you mean assemble the SQL in Code.
I am using MYSQL 4.1 and PHP.
Ah. Looking closer, I see that you're not using an outside variable in
the CASE bit. Sorry about that. Should have read closer.
In your FROM clause, you could have stuff like:
FROM bonus b
JOIN
mos wrote:
Phil,
FabForce doesn't work with MySQL 5 because of the new password
encryption. Fabforce never lets me connect to a database. I suppose I
could revert back to the old PW mgt scheme but that may weaken the security.
There was an earlier post on this list which discussed
I'm looking for a free, perhaps open source, case tool for MySQL 5.x.
(Older MySQL 4.0 case tools may not work because of the changes to pw
security in 4.1 and later)
I tried MySQL Workbench 1.1.5 alpha but I keep getting errors The
following error occurred while launching the object editor
mos,
I'm looking for a free, perhaps open source, case tool for MySQL 5.x.
(Older MySQL 4.0 case tools may not work because of the changes to pw
security in 4.1 and later)
I tried MySQL Workbench 1.1.5 alpha but I keep getting errors The
following error occurred while launching the object
Ysgrifennodd Philip Mather:
http://fabforce.net/dbdesigner4/ ...is pretty funky and meets the
requirements.
Phil
But had, the last time I looked, been discontinued in favour of MySQL
Workbench.
Have you (the OP, that is) tried to sort out why MySQL Workbench isn't
playing? I have it on my
At 09:58 AM 12/8/2006, you wrote:
mos,
I'm looking for a free, perhaps open source, case tool for MySQL 5.x.
(Older MySQL 4.0 case tools may not work because of the changes to pw
security in 4.1 and later)
I tried MySQL Workbench 1.1.5 alpha but I keep getting errors The
following error
[EMAIL PROTECTED] wrote:
Hi Andy,
Two questions for you:
1) Why store so many repeatable data in the same table?
I mean you needn't to store purchases/previews for all records.
You can choose MySql SET datatype, or you can choose another table to
store the action types and let the original
Hi,
I'm not a wizard on the MySQL optimizer, but here's my go...
Two questions for you:
1) Why store so many repeatable data in the same table?
I mean you needn't to store purchases/previews for all records.
You can choose MySql SET datatype, or you can choose another table to
store
: [EMAIL PROTECTED]
Subject: Index effectivity for a 2-valued field (was Re:
Should I use an index in this case?)
[EMAIL PROTECTED] wrote:
Hi Andy,
Two questions for you:
1) Why store so many repeatable data in the same table?
I mean you needn't to store purchases/previews for all
I have a table that is roughly like the below:
id - PK, autoincremented integer
name - varchar
visit- timestamp
action - char(10)
Now, 'action', while a char(10), is only ever intended
to contain two possible values, purchase and
preview.
The table might end up containing tens
Hi Andy,
Two questions for you:
1) Why store so many repeatable data in the same table?
I mean you needn't to store purchases/previews for all records.
You can choose MySql SET datatype, or you can choose another table to
store the action types and let the original table refers to it.
So that you
Hi,
My MySQL on Debian is on version 4.0.24_Debian-10sarge1-log. I have a
varchar(255) as a primary key for a table. I have found the primary key case
insensitive. Is this normal? This is not the behavior I prefer. Any help
would be appreciated, thanks.
Timothy
On 10/15/06, Timothy Wu [EMAIL PROTECTED] wrote:
Hi,
hi
My MySQL on Debian is on version 4.0.24_Debian-10sarge1-log. I have a
varchar(255) as a primary key for a table. I have found the primary key
case
insensitive. Is this normal?
Yes, it's normal!
To force mysql to use case-sensitive
At 08:26 AM 10/15/2006, you wrote:
Hi,
My MySQL on Debian is on version 4.0.24_Debian-10sarge1-log. I have a
varchar(255) as a primary key for a table. I have found the primary key case
insensitive. Is this normal? This is not the behavior I prefer. Any help
would be appreciated, thanks
On 10/16/06, mos [EMAIL PROTECTED] wrote:
Timothy,
You can make the varchar column case sensitive by using the
binary
attribute or use the isstrcmp(value1,value2) for an exact match.
See http://lists.mysql.com/mysql/170390
varchar(255) binary
or select binary 'a'='A' ...
Mike
One database, multiple tables.
I need to limit access to one table per user, but also allow all other
tables to be accessed by all users. For example:
Say I have 5 users: usera, userb, userc, userd, usere
Table 1 - all 5 users, select, inset, update, delete
Table 2 - all 5 users, select,
hi all...
i found this on the mysql dev manual site:
MySQL 4 and later string comparisons, including DISTINCT, aren't case
sensitive unless the field is declared as BINARY or you use BINARY in your
comparison.
so here i tried it but no good. any ideas?! the field is not declared
binary but i do
kalin mintchev wrote:
hi all...
i found this on the mysql dev manual site:
MySQL 4 and later string comparisons, including DISTINCT, aren't case
sensitive unless the field is declared as BINARY or you use BINARY in your
comparison.
so here i tried it but no good. any ideas?! the field
http://dev.mysql.com/doc/refman/5.1/en/charset-binary-op.html
It has some good examples.
got it thanks...
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Hello,
I am using MySql-5.0.21 on Suse-Linux-10, i created tables using
lowercase names
for example ;
mysql create table a (id int);
Query OK, 0 rows affected (0.04 sec)
mysql select * from A;
ERROR 1146 (42S02): Table 'mysql.A' doesn't exist
mysql select * from a;
Empty set (0.01 sec)
I have
Hello,
I am using MySql-5.0.21 on Suse-Linux-10, i created tables using
lowercase names
for example ;
mysql create table a (id int);
Query OK, 0 rows affected (0.04 sec)
mysql select * from A;
ERROR 1146 (42S02): Table 'mysql.A' doesn't exist
mysql select * from a;
Empty set (0.01 sec)
I have
Hi,
yes it makes a huge difference,
as the tables are stored in files and therefore if
the filesystem is case-insensitive (Windows) you can
use either case in your queries, while on a case-sensitive
filesystem (linux etc) you can't.
See: http://dev.mysql.com/doc/refman/5.0/en/cannot-find
will certainly take a closer look at your suggestions !
Regards, Cor
- Original Message -
From: Rhino [EMAIL PROTECTED]
To: C.R.Vegelin [EMAIL PROTECTED]; mysql@lists.mysql.com
Sent: Tuesday, May 09, 2006 2:42 PM
Subject: Re: How to convert strings to 'proper case' ?
I'd be surprised if things
to choose which records to change/keep/delete.
May not be the best way, but it would work.
I'm giving it a go, but it's been running for about 4 hours at 60%
CPU so far! Would it be quicker to tell it to use a case insensitive
collation to locate the duplicates?
Marcus
--
Marcus Bointon
On 9 May 2006, at 13:12, Marcus Bointon wrote:
I'm giving it a go, but it's been running for about 4 hours at 60%
CPU so far! Would it be quicker to tell it to use a case
insensitive collation to locate the duplicates?
I managed to come up with a variation on my original attempt
, 2006 8:12 PM
Subject: Re: Case confusion
On 9 May 2006, at 02:22, Chris wrote:
I would run this query:
SELECT
*
FROM mytable
WHERE LOWER(emailaddress) IN
(SELECT
LOWER(emailaddress)
FROM mytable
GROUP BY 1
HAVING COUNT(emailaddress) 1)
This would show all duplicate
An example of how to make the first letter in a string uppercase -
analogous to UCFIRST
SELECT CONCAT(UPPER(SUBSTRING(firstName, 1, 1)),
LOWER(SUBSTRING(firstName FROM 2))) AS properFirstName
/quote
/Johan
C.R.Vegelin wrote:
Hi List,
I want to convert strings to proper-case,
where only
: A Diplomatic History of the
UN)
- A.b. Mcdonald? (more likely: A. B. McDonald)
- The Life And Times Of King George Iii? (more likely: The Life and Times of
King George III)
In any case, I don't think a simple SQL UPDATE will do what you want to do,
at least not very easily. You'll almost
My God!
Rhino, that was a very long and very good answer!!
Impressive!!
/Johan
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Marcus,
I just noticed that a key field (emailaddress) in my db is case
sensitive when it should not have been, so now I've got a bunch of
what are effectively duplicate records. I'm having trouble picking
them out so I can manually merge/delete them before changing the
collation on the field
I just noticed that a key field (emailaddress) in my db is case
sensitive when it should not have been, so now I've got a bunch of
what are effectively duplicate records. I'm having trouble picking
them out so I can manually merge/delete them before changing the
collation on the field
/delete.
May not be the best way, but it would work.
Chris
Marcus Bointon wrote:
I just noticed that a key field (emailaddress) in my db is case
sensitive when it should not have been, so now I've got a bunch of
what are effectively duplicate records. I'm having trouble picking
them out so I can
Hi List,
I want to convert strings to proper-case,
where only the 1st char of each word is uppercase,
such as: This Is An Example.
Any idea how to do this with MySQL 5.0.15 ?
Thanks, Cor
1 - 100 of 424 matches
Mail list logo
