From: | Phil Jackson <sapient(at)clear(dot)net(dot)nz> |
---|---|
To: | adrian(dot)klaver(at)gmail(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Cannot open table in new database |
Date: | 2010-07-01 19:11:09 |
Message-ID: | 4C2CE84D.6030104@clear.net.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Adrian
I had missed that bit. That makes sense now.
Cheers
Phil Jackson
On 6/30/2010 5:04 PM, Adrian Klaver wrote:
> On Thursday 01 July 2010 11:11:29 am Phil Jackson wrote:
>
>> Hi Adrian
>>
>> The link says that;
>>
>> "Identifier and key word names are case insensitive."
>>
>> But I have renamed the source table in lowercase and this gets me one
>> step further.
>>
>> I'll carry on and see what happens next.
>>
>> Cheers
>>
>> Phil Jackson
>>
>>
> You need to go to bottom of that section where you would find :)
>
> "Quoting an identifier also makes it case-sensitive, whereas unquoted names are
> always folded to lower case. For example, the identifiers FOO, foo, and "foo"
> are considered the same by PostgreSQL, but "Foo" and "FOO" are different from
> these three and each other. (The folding of unquoted names to lower case in
> PostgreSQL is incompatible with the SQL standard, which says that unquoted
> names should be folded to upper case. Thus, foo should be equivalent to "FOO"
> not "foo" according to the standard. If you want to write portable applications
> you are advised to always quote a particular name or never quote it.) "
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2010-07-01 20:44:24 | Re: problems with encoding and accent letters |
Previous Message | Thomas Markus | 2010-07-01 18:26:14 | Re: Uncable to commit: transaction marked for rollback |