- Original Message -
> From: "Eric Bergen"
>
> 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.
Ye gods, it's an outbreak of common sense! Someone quarantine that man before
it spreads!
In all se
uments 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 of p
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
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 sensitive because -P and -p mean different things. The
> s
case sensitive because -P and -p mean different things. The
short options are case sensitive so the long options may as well be.
It keeps things simpler. Who wants to write --Port when --port means
not hitting the shift key?
There are a few exceptions to this. The option comparison treats _ and
- as the sa
like
> my work but with crappy quality and terrible 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 co
and i
> know a lot of crap out there which is more popluar like
> my work but with crappy quality and terrible 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 wh
:
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
signature.asc
Description: OpenPGP digital signature
Hi,
On Sun, Nov 18, 2012 at 4:35 PM, Reindl Harald wrote:
>
>
> 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?
>
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 cur
Hi, Reindl,
On Sun, Nov 18, 2012 at 3:11 PM, Reindl Harald wrote:
>
>
> 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?
> &g
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&qu
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
>
> 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]
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?! t
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 declar
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
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 hav
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 hav
* from user where username='John'"; //returns one row
> "select * from user where username='john'"; //returns one row
>
> The records in the database has username 'John'.
>
> Wh
he database has username 'John'.
Why it isn't case sensitive? 'John" and 'john' .. are two different strings..?
Because it isn't. String comparisons are case insensitive by default in
mysql <http://dev.mysql.com/doc/mysql/en/case-sensitivity.html>
Column type is username varchar(100).
When I do select from database:
"select * from user where username='John'"; //returns one row
"select * from user where username='john'"; //returns one row
The records in the database has username
is there an option to perform mysqldump to a file and to have the case sensitiveness
of the tables saved as well in windows os? (I had all tables in lower case)...
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTE
You may need to user lower_case_names = 0 to turn off the case sensitivity
on the unix system since windows is not case sensitive.
-Original Message-
From: Ben David, Tomer
To: [EMAIL PROTECTED]
Sent: 7/27/04 5:56 AM
Subject: dump case sensitive windows
Hi
I'm using mysqldump in wi
Hi
I'm using mysqldump in windows
and importing the tables in unix
the tables are all dumped in lowercase although they had mixed case... can i tell
mysqldump to dump with case sensitive on windows?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubs
Java is case sensitive, this is the way JDBC wants you to work. The
Exception is generated by JDBC, not due to an error from MySQL. I would
recommend checking JDBC documentation.
Aman Raheja
http://www.techquotes.com
On Wed, 2004-07-21 at 10:55, Ying Lu wrote:
> Hello,
>
> I have a
Hello,
I have a question about column name case sensitive. Currently, we use
MySQL 3.23.32 running on Linux.
I am trying to use JDBC to get email from table T1
T1(
id char(3),
name varchar(12),
Emailvarchar(16)
)
Now If I say,
try{
...
String email =
getString("
Hello,
I have a question about column name case sensitive. Currently, we use
MySQL 3.23.32 running on Linux.
I am trying to use JDBC to get email from table T1
T1(
id char(3),
name varchar(12),
Emailvarchar(16)
)
Now If I say,
try{
...
String email =
getString("
nt: Tuesday, May 18, 2004 4:00 PM
Subject: Re: InnoDB case sensitive collation
> Matt Mastrangelo <[EMAIL PROTECTED]> wrote:
> > How can an InnoDB table be created with case sensitive collation? The
> > example below creates two identical tables, one MyISAM and the other
> &
I'm using version 4.1.1-alpha, running on RedHat Linux 9.
Victoria Reznichenko wrote:
Matt Mastrangelo <[EMAIL PROTECTED]> wrote:
How can an InnoDB table be created with case sensitive collation? The
example below creates two identical tables, one MyISAM and the other
InnoDB. The I
Matt Mastrangelo <[EMAIL PROTECTED]> wrote:
> How can an InnoDB table be created with case sensitive collation? The
> example below creates two identical tables, one MyISAM and the other
> InnoDB. The InnoDB fails when inserting primary keys that differ in case
> only. Wha
How can an InnoDB table be created with case sensitive collation? The
example below creates two identical tables, one MyISAM and the other
InnoDB. The InnoDB fails when inserting primary keys that differ in case
only. What am I doing wrong?
Thanks.
drop database test;
create database test
you can add
`lower_case_table_names = 1` to the my.cnf to ignore table name sensitivity.
-Original Message-
From: Andre MATOS
To: [EMAIL PROTECTED]
Sent: 5/12/04 9:53 AM
Subject: Case Sensitive
Hi List,
I have three MySQL servers. One is running on Windows XP, another on
MacOS
X, and
etails, and be sure to read the last sentence.
Michael
Jack Coxen wrote:
This isn't caused by MySQL. It's an OS issue. Linux and Unix are case
sensitive operating systems so any program you run, unless it is
specifically written to be NON-case sensitive, is case sensitive as well.
Jac
This isn't caused by MySQL. It's an OS issue. Linux and Unix are case
sensitive operating systems so any program you run, unless it is
specifically written to be NON-case sensitive, is case sensitive as well.
Jack
-Original Message-
From: Andre MATOS [mailto:[EMAIL PROTE
tables names (is
not case sensitive). However, in the Linux I have problems (it follows
exactly the name uppercase and lowercase is case sensitive).
So, for example:
On Windows/Mac: TestABC is created as testabc
On Linux: TestABC is created as TestABC
1) How can I disable this in the MySQL
machine every hour.
However, this is producing errors because the MySQL installation on
the local machine isn't case sensitive, therefore it isn't
recognizing the same tables. How can I rectify this, I can't find
any documentation on the MySQL site regarding this
note: I don't know anything about webyog, but MySQL's built-in
replication works so well, I'd recommend looking into using it.
However, this is producing errors because the MySQL installation on
the local machine isn't case sensitive, therefore it isn't recognizing
t
errors because the MySQL installation on the
local machine isn't case sensitive, therefore it isn't recognizing the same
tables. How can I rectify this, I can't find any documentation on the MySQL
site regarding this...?
Thank
At 12:44 AM 12/27/2003, Michael Stassen wrote:
You're welcome. I did suggest some (not very elegant) SQL in my first
note. I take it that didn't turn out to be useful. It's possible that if
you were to describe why not, someone could make a better suggestion. Of
course, I suppose you may hav
You're welcome. I did suggest some (not very elegant) SQL in my first
note. I take it that didn't turn out to be useful. It's possible that
if you were to describe why not, someone could make a better suggestion.
Of course, I suppose you may have already solved this in Delphi.
mos wrote:
C
Chris & Michael,
Thanks for the feedback. I was hoping it could be done in SQL without
using Perl since I don't have any experience with it. But I can use some
of the ideas you gave me to create a Delphi program quick enough. Thanks
again. :)
Mike
--
MySQL General Mailing List
For list ar
Michael Stassen wrote:
> You are right that perl can do the search and replace in one line, but
> you'll need some more code to read and write the data, either from <
> > mysql or from a source file before importing into mysql. That's
why I > said "almost" a one-liner.
>
> You are also right th
Chris W wrote:
Michael Stassen wrote:
mos wrote:
Ok, put your thinking caps on because this one bit of a toughie.
I an Update statement that will insert a '/' in front of the *first*
lowercase letter of a field value.
Example: "ABCDef" becomes "ABCD/ef".
Of course it doesn't always end in "ef"
Michael Stassen wrote:
mos wrote:
Ok, put your thinking caps on because this one bit of a toughie.
I an Update statement that will insert a '/' in front of the *first*
lowercase letter of a field value.
Example: "ABCDef" becomes "ABCD/ef".
Of course it doesn't always end in "ef" and could be an
mos wrote:
Ok, put your thinking caps on because this one bit of a toughie.
I an Update statement that will insert a '/' in front of the *first*
lowercase letter of a field value.
Example: "ABCDef" becomes "ABCD/ef".
Of course it doesn't always end in "ef" and could be any 2 or 3 group of
lette
Ok, put your thinking caps on because this one bit of a toughie.
I an Update statement that will insert a '/' in front of the *first*
lowercase letter of a field value.
Example: "ABCDef" becomes "ABCD/ef".
Of course it doesn't always end in "ef" and could be any 2 or 3 group of
letters like "AB
n values that start with Aor a. If you want to make this
search case-sensitive, use something like INSTR(col_name, "A")=1 to
check a prefix. Or use STRCMP(col_name, "A") = 0 if the column value
must be exactly "A" .
Simple comparison operations ( >=, >, = ,
. They result are all the same.
However, if I want to retrieve only 'sandy' instead of 'Sandy'. Is there any
query to achieve that?
Is there anyway to configure mysql to be case sensitive?
Thanks!
Hsiu-Hui
--
MySQL General Mailing List
For list archives: http://lists.mysql.c
"gord barq" <[EMAIL PROTECTED]> wrote:
>
> I'm using MySQL 4.1 so how do I define case sensitive collation? Is it on
> the columns or on the indexes?
On column. Look at the collations of your character set using SHOW COLLATION command:
http://www
I'm using MySQL 4.1 so how do I define case sensitive collation? Is it on
the columns or on the indexes?
Thanks.
From: Victoria Reznichenko <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Case sensitive indexes
Date: Tue, 26 Aug 2003 13:18:19 +0300
"gord barq" <
"gord barq" <[EMAIL PROTECTED]> wrote:
> I have the following index:
>
> CREATE UNIQUE INDEX SongTopic_idx ON SongTopic(songTitle, artist, album);
>
> Where songtitle, artist and album are varchar() columns.
>
> It appears that this index is not case sens
2003年 8月 26日 火曜日 09:33、gord barq さんは書きました:
> I have the following index:
>
> CREATE UNIQUE INDEX SongTopic_idx ON SongTopic(songTitle, artist, album);
>
> Where songtitle, artist and album are varchar() columns.
>
> It appears that this index is not case sensitive. Is that c
I have the following index:
CREATE UNIQUE INDEX SongTopic_idx ON SongTopic(songTitle, artist, album);
Where songtitle, artist and album are varchar() columns.
It appears that this index is not case sensitive. Is that correct? If so,
how can I have it so that it is indeed case sensitive because
n" <[EMAIL PROTECTED]>; "Matt Gostick"
<[EMAIL PROTECTED]>
Sent: Monday, March 31, 2003 10:13 AM
Subject: Re: Case-Sensitive database
> On 31 Mar 2003 at 9:49, Dan Tran wrote:
>
> > I wont work for me, I dont have access to SQL layer.
>
> You can d
e login = "Matt"
> >and binary login = "Matt";
> >
> > I do it twice b/c the binary operation is quite slow and doing the
> > normal equate first speeds it up significantly.
The binary operation is slow because it's not using the index. If
you
esn't exactly answer your question... sorry.
Matt Gostick.
On Mon, 2003-03-31 at 11:23, Dan Tran wrote:
>
> Hi, how do I configure mysql to be Case-Sensitive globally?
> (ie where, like, clauses work with case-sensitive strings
>
> Help is greatly appreciated.
>
> -Dan
>
I wont work for me, I dont have access to SQL layer.
I use JDO
In Micorosft SQL Server I can specify the Collate during database creation
to make my string case-sensitive. Is there an equivalent configuration for
MySQL?
Thanks ahead for all suggestions
-Dan
- Original Message -
From
Hi, how do I configure mysql to be Case-Sensitive globally?
(ie where, like, clauses work with case-sensitive strings
Help is greatly appreciated.
-Dan
gt; MySQL is case insensitive in selecting records...
> how to make it case-sensitive in selecting records...
SELECT BINARY ...
/ Carsten
--
Carsten H. Pedersen
keeper and maintainer of the bitbybit.dk MySQL FAQ
http://www.bitbybit.dk/mysqlfaq
--
Hi,
I have a situation as follows:
There is a table that stores the user name.
One user name is 'David' and another is 'david'
I want to select only the user with the name
'david'(all small and not 'David')
MySQL is case insensitive in selecting rec
LISTUS VALUES ('IUSB-2348A-N00021','US','eng','FUEL TANK
> SUPPORTS, LH');
>
> I get an error:
>
> ERROR 1062: Duplicate entry 'IUSB-2348A-N00021-US-eng' for key 1
>
> Is it possible to set mySQL to be case sensitive since it'
error:
ERROR 1062: Duplicate entry 'IUSB-2348A-N00021-US-eng' for key 1
Is it possible to set mySQL to be case sensitive since it's a small difference between
the two?
Best regards
Joacim Järkeborn
Sweden
--
Jane ...
(This is based on our own experience, and info found in the MySQL Manual
... http://www.mysql.com/doc/N/a/Name_case_sensitivity.html). We have used
this procedure to convert dozens of databases, and found that setting the
server's variable to lower-case tables also requires converting
: <[EMAIL PROTECTED]>
Sent: Monday, July 02, 2001 8:37 AM
Subject: Windows 2000 MySQL case sensitive?
> Hi All,
> I have recently installed MySQL on my windows 2000 machine and
> everything is great except for the fact that it doesnt't seem to recognize
> upper case table /
case and hence, noneof
> the code works! (It's impractical for me to convert all the code)
Mysql column name isn't case sensitive att all. the table name is depend
on OS, so
windows 200 is not case sensisitve. YOu should chek your code
Hi All,
I have recently installed MySQL on my windows 2000 machine and
everything is great except for the fact that it doesnt't seem to recognize
upper case table / column names? This wouldn't be a problem if I was just
developing locally because I could just name everything lowercase. Th
ame)= upper('whater I am searching
>>for');
>>
>>Cal
>>http://www.calevans.com
>>
>>
>>-Original Message-
>>From: [EMAIL PROTECTED]
>>[mailto:[EMAIL PROTECTED]]On Behalf
>>Of MikeBlezien
>>Sent: Thursday, March 22,
On Thu, 22 Mar 2001 22:27:06 +, Jordan Elver <[EMAIL PROTECTED]>
wrote:
Ignore this post! My fault, we had something coded wrong in the script.! It
works fine now.
My apologies to the list! :(
>>If you add BINARY to the column it WILL make it case sensitive.
>>
>>O
Try
Select * from table where upper(bus_name)= upper('whater I am searching
for');
Cal
http://www.calevans.com
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf
Of MikeBlezien
Sent: Thursday, March 22, 2001 4:02 PM
To: [EMAIL PROTECTED]
Sub
If you add BINARY to the column it WILL make it case sensitive.
On Thursday 22 March 2001 22:01, you wrote:
> Hello All,
>
> I have a table with a column called "bus_name" varchar(100) which is used
> in a Business Name search form. I need to make the Business Name that
Hello All,
I have a table with a column called "bus_name" varchar(100) which is used in a
Business Name search form. I need to make the Business Name that is entered into
the search form case in-sensitive to the column "bus_name" IE. If we have a
entry in the column "bus_name" "The Happy Shop", a
A comparison will be case sensitivie, if any sub-part of the expression
is case sensitive. There are several ways to solve this:
1) CREATE or ALTER your tables so that the relevant CHAR and
VARCHAR fields are of type BINARY; change TEXTs to BLOBs
2) Use a case-sensitive, but neutral function
Jiøí Mikulá¹ wrote:
>
> Hi all.
> I have problem with MySQL 3.23.32 on FreeBSD4.2
> SELECTs are not case sensitive, any suggestion how to set it ?
> I'v looked into DOCs, but i'm not so clever from it :(( ...
> my config options was only
>
> ./configure --prefi
Hi all.
I have problem with MySQL 3.23.32 on FreeBSD4.2
SELECTs are not case sensitive, any suggestion how to set it ?
I'v looked into DOCs, but i'm not so clever from it :(( ...
my config options was only
./configure --prefix=/usr/local/mysql
Many thaks.
Jiri Mikulas
[EMAIL PROTE
75 matches
Mail list logo
