Search Postgresql Archives

Re: quoted identifier behaviour

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> Are there plans to make Postgresql's behavior SQL compliant with regards 
> to quoted identifiers?

No.

> My specific need is to access tables named in lower case by an uppercase 
> quoted identifier, which is in line with the SQL standard.  So if I created 
> table foo, I should be able to access it like "FOO".  Is there a configuration 
> options that modifies this behavior or can I change the names in the system tables?

No configuration option, but you can always rename tables with

ALTER TABLE foo RENAME TO "FOO"

Simple creating the table as "FOO" in the first place avoids the problem as well. 
Be aware that using uppercase identifiers means that *all* access to that table must 
now quote the name.

- --
Greg Sabino Mullane greg@xxxxxxxxxxxx
PGP Key: 0x14964AC8 200703141312
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8

-----BEGIN PGP SIGNATURE-----

iD8DBQFF+C2PvJuQZxSWSsgRAw/XAJ9gE9lskT7yBQUbJsIa8mSPyxmc/wCgrFJx
EWX65PmQaWUIr5MCDykXJN4=
=LyWH
-----END PGP SIGNATURE-----




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux