On Wed, May 21, 2014 at 4:50 AM, Hartmut Holzgraefe 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
>> individual t
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 colum
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
- Original Message -
> From: "Reindl Harald"
> 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 t
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
>> t
On Tue, May 20, 2014 at 5:52 PM, Hartmut Holzgraefe wrote:
> On 05/20/2014 11:10 PM, Larry Martell wrote:
>
>> 5.5 server:
>>
>> mysql> select distinct(pnlCurrency) from PnLDetail;
>> +-+
>> | pnlCurrency |
>> +-+
>> | USD |
>> | USd |
>> +-+
>>
On 05/20/2014 11:10 PM, Larry Martell wrote:
> 5.5 server:
>
> mysql> select distinct(pnlCurrency) from PnLDetail;
> +-+
> | pnlCurrency |
> +-+
> | USD |
> | USd |
> +-+
> 2 rows in set (0.00 sec)
>
> 5.0 server:
>
> mysql> select distinct(pn
On Tue, May 20, 2014 at 9:38 AM, Hartmut Holzgraefe 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 of
>
> SHOW VARIA
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_%'
Am 20.05.2014 15:26, schrieb Larry Martell:
> I have 2 servers, one is running 5.5.25a and the other 5.0.77.
>
> They both have the same collation and character set:
>
> mysql> SELECT COLLATION(VERSION());
> +--+
> | COLLATION(VERSION()) |
> +--+
> | utf8_
At 16:01 -0600 3/16/06, Sterling Anderson wrote:
On Mar 16, 2006, at 3:49 PM, Paul DuBois wrote:
This fails however. 'g/dl' != 'g/dL' though. I don't get why a
string field is being treated this way. I understand the HFS+
filesystem is not case sensitive but that shouldn't be an issued
with v
On Mar 16, 2006, at 3:49 PM, Paul DuBois wrote:
This fails however. 'g/dl' != 'g/dL' though. I don't get why a
string field is being treated this way. I understand the HFS+
filesystem is not case sensitive but that shouldn't be an issued
with varchar fields should it?
No, it's not a file
At 15:22 -0600 3/16/06, Sterling Anderson wrote:
I'm running MySQL 5.0.18 on OS X 10.4.5, on an intel MacBook. My
table definition is:
CREATE TABLE `UNIT` (
`UNIT_ID` int(11) NOT NULL auto_increment,
`UNIT_CODE` varchar(50) default NULL,
`UNIT_DESC` varchar(50) default NULL,
`USER_ID` i
Can this also be used? (just now figured out a way)
SELECT
bo.book,
b.chapter,
b.verse,
b.text
FROM
avkjv.books bo
LEFT JOIN
Instead of using COLLATE you can try using the "BINARY" option
instead. It will work in older versions of MySQL and I think it makes
you select a bit more readable. Just put "BINARY" before the
comparison you want to be case sensitive.
WHERE BINARY text LIKE '%Jehovah%'
On Nov 8, 2005, at
At 13:00 -0500 12/17/03, Mayuran Yogarajah wrote:
Paul DuBois wrote:
At 12:22 -0500 12/17/03, Mayuran Yogarajah wrote:
I am using case sensitive table names when I create tables
like :
CREATE TABLE MyTest;
If I want to do a select from this table, I have to do
SELECT * FROM MyTest, not SELECT *
Paul DuBois wrote:
At 12:22 -0500 12/17/03, Mayuran Yogarajah wrote:
I am using case sensitive table names when I create tables
like :
CREATE TABLE MyTest;
If I want to do a select from this table, I have to do
SELECT * FROM MyTest, not SELECT * FROM mytest.
How can I make it so that the table n
At 12:22 -0500 12/17/03, Mayuran Yogarajah wrote:
I am using case sensitive table names when I create tables
like :
CREATE TABLE MyTest;
If I want to do a select from this table, I have to do
SELECT * FROM MyTest, not SELECT * FROM mytest.
How can I make it so that the table name is still MyTest
b
At 17:51 -0500 3/2/03, Sunfire wrote:
hi i have a delete query that will delete a record based on the company
name:
delete from members where company='$company';
the query works fine and all but there is a problem because if there is more
than 1 company listed but with different use of case in thei
You can specify a varchar field as binary, for instance: field1 varchar(50)
binary
query, sql
Mike
-Original Message-
From: asp52 [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 9:50 AM
To: Mike Grabski; [EMAIL PROTECTED]
Subject: Re: Case sensitivity
Thanks,
Just worked
See http://www.mysql.com/doc/en/CHAR.html or
http://www.mysql.com/doc/en/BLOB.html .
If your column types are CHAR or VARCHAR insert BINARY.
If your column type is TEXT, change to BLOB.
--
You said
Hi,
I have been search
>
To: "'asp52'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, December 19, 2002 2:29 PM
Subject: RE: Case sensitivity
> You have two choices, you can use a binary datatype for the field, or
force
> a binary comparison usin
You have two choices, you can use a binary datatype for the field, or force
a binary comparison using the BINARY operator.
http://www.mysql.com/doc/en/Case_Sensitivity_Operators.html
http://www.mysql.com/doc/en/Column_types.html
query, sql
Mike
-Original Message-
From: asp52 [mailto:
Mark:
Do you have my.ini (or my.cfg) set to ignore case in table names?
set-variable = lower_case_table_names=1
Gerald Jensen
- Original Message -
From: "Mark Weiler" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, June 24, 2002 5:56 PM
Subject: Case Sensitivity for CHECK
Hi!
The fact that foreign key definitions do not honor lower_case_table_names=1
is mentioned in the manual. I have added the fix to this on the TODO list
for July 2002.
You have found the right place, this mailing list is the right place to
report bugs in InnoDB.
Best regards,
Heikki Tuuri
Inn
At 11:17 AM 3/14/2002, you wrote:
>On Thursday 14 March 2002 9:32 am, BD wrote:
> >
> > Why or why couldn't MySQL have used case insensitive names in the first
> > place? Store everything in lower case internally, but allow the user to use
> > "Invoice_Number" or "invoice_number" or "INVOICE_NUMBE
On Thursday 14 March 2002 9:32 am, BD wrote:
>
> Why or why couldn't MySQL have used case insensitive names in the first
> place? Store everything in lower case internally, but allow the user to use
> "Invoice_Number" or "invoice_number" or "INVOICE_NUMBER" in the SQL
> statement and it should ref
At 02:05 AM 3/14/2002, you wrote:
>Hi,
>I run mysql on windows as well as linux.
>table creation and access right are given by java program.
>
>Problem im facing is.,
>i create a table with name TEMP
>in windows in creates table with name "temp" and linux "TEMP"
>while giving rights thru GRANTst
Hi.
On Sun, Feb 17, 2002 at 09:10:24AM -0700, [EMAIL PROTECTED] wrote:
> Since my first posting of this came out all screwed up,
>
> I currently have a PHP script performing the following query:
> mysql_query("SELECT * FROM Stuff WHERE Release LIKE \"%$var2%\"",$var1)
>
> It works great except
> I'm having trouble with what appears to be a case sensitivity issue.
> Essentially, when I use the "right" case for a table name, the query fails,
> but when I use the wrong case, the query succeeds.
Well, it seems to depend on the system you are using. I noticed
that when I created tables thro
Select Name, lower(name) as sortOrder from users order by sortOrder;
Not exactly what you wanted, but closer.
Cal
http://www.calevans.com
-Original Message-
From: Kif Henderson [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 09, 2001 7:38 PM
To: [EMAIL PROTECTED]
Subject: Case Sensitiv
31 matches
Mail list logo
