[HACKERS] Case Sensitivity
Is there a way to set case sensitivity on? Thanks in advance juan
Re: [HACKERS] Case Sensitivity
Ola' juan, Is there a way to set case sensitivity on? No. Discussions about this thread are in the archives (http://archives.postgresql.org). Take a look at: http://www.postgresql.org/docs/8.0/interactive/sql-syntax.html#SQL-SYNTAX-IDENTIFIERS Euler Taveira de Oliveira euler[at]yahoo_com_br Yahoo! Acesso Grátis - Internet rápida e grátis. Instale o discador agora! http://br.acesso.yahoo.com/ ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] Case Sensitivity
On Sat, Apr 09, 2005 at 21:02:34 +0200, [EMAIL PROTECTED] wrote: Is there a way to set case sensitivity on? In what context? If you are talking about mixed case table or column names, then you need to quote them with double quotes (). ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[HACKERS] case sensitivity in PQExecPrepared
I noticed a curious thing (not sure if by design or not). While using the PQExecPrepared interface, the statement name passed to the function (as a const char*) has to be in lower case to get it to work. I kind of understand why this is, but it is kind of weird that passing the exact same statement name to PQExecPrepared and PREPARE does not work if it contains any upper case characters. Just FYI. Merlin ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] case sensitivity in PQExecPrepared
Merlin Moncure wrote: While using the PQExecPrepared interface, the statement name passed to the function (as a const char*) has to be in lower case to get it to work. I kind of understand why this is, but it is kind of weird that passing the exact same statement name to PQExecPrepared and PREPARE does not work if it contains any upper case characters. PQExecPrepared is used in C programs, PREPARE is used in SQL programs. I think it's fairly obvious that those use different syntax rules. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] case sensitivity in PQExecPrepared
Peter Eisentraut wrote: Merlin Moncure wrote: While using the PQExecPrepared interface, the statement name passed to the function (as a const char*) has to be in lower case to get it to work. I kind of understand why this is, but it is kind of weird that passing the exact same statement name to PQExecPrepared and PREPARE does not work if it contains any upper case characters. PQExecPrepared is used in C programs, PREPARE is used in SQL programs. I think it's fairly obvious that those use different syntax rules. Well, yes :) Just to be absolutely clear what I mean, the following will fail (pseudocode, but you get the idea): char stmt[] = prepare X as select 0(); PQexec(c, execute X); -- works PQexecPrepared(c, X [...]); -- fails You are saying this is the correct and expected behavior? Merlin ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] case sensitivity in PQExecPrepared
Merlin Moncure wrote: Well, yes :) Just to be absolutely clear what I mean, the following will fail (pseudocode, but you get the idea): char stmt[] = prepare X as select 0(); PQexec(c, execute X); -- works PQexecPrepared(c, X [...]); -- fails You are saying this is the correct and expected behavior? Yes, because part of those syntax rules is that in SQL, unquoted identifiers are folded to lower case, but in C they are not. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
