On Thu, Jul 4, 2013 at 1:17 AM, Tom Lane wrote:
> Quite aside from implementation difficulty, restricting the change to
> just column aliases doesn't make it more palatable. You'd entirely lose
> the argument that the change increases spec compliance, because the spec
> is perfectly clear that a
On Thu, Jul 4, 2013 at 1:36 AM, Bruce Momjian wrote:
> And let's not forget that column aliases can be used as indentifiers in
> queries:
>
> test=> SELECT 1 AS x
> test-> ORDER BY x;
> x
> ---
> 1
> (1 row)
>
> test=> SELECT 1 AS "X"
>
On Thu, Jul 4, 2013 at 12:38 AM, Alvaro Herrera wrote:
> Aliases are treated just like any other identifier. The downcasing
> happens in the lexer (src/backend/parser/scan.l), which is totally
> unaware of the context in which this is happening; so there's no way to
> tweak the downcasing behavio
On Wed, Jul 3, 2013 at 9:50 PM, Tom Lane wrote:
> > Any plans to fix this in next release or having a patch to fix this?
>
> No.
>
> This has been discussed (many times) before. There isn't any feasible
> way to change this behavior without breaking an incredible amount of
> code, much of which
On Wed, Jul 3, 2013 at 9:35 PM, Thomas Kellerer wrote:
> I wonder why you need that. I never had the requirement for that.
>
> Which driver/interface do you use that requires an alias to be all
> uppercase?
Looks like you didn't get me, am not saying aliases to be all upper case by
default (BTW
On Wed, Jul 3, 2013 at 9:05 PM, Bruce Momjian wrote:
> Yes, both the identifier names and alias names are folded to lower case.
> I never thought of them as different, but you are right, they are, and
> we are non-standard in both areas. Sorry.
Any plans to fix this in next release or having a
On Wed, Jul 3, 2013 at 8:54 PM, Bruce Momjian wrote:
> Agreed. The original poster specifically wanted "MYTABLE" and mytable
> to be the same, not "mytable" and mytable. Postgres is certainly
> non-standard in this area. I think the ability visiually distinguish
> lower-case letters better tha
Thanks!
Sure this is not a bug. Just want to know if there is any possible way to
achieve this.
Reason being - need to change all the data layer of project where the
column mapping has been done with Upper Case.
Regards...
Resending
On Wed, Jul 3, 2013 at 2:42 PM, Dev Kumkar wrote:
> Hello,
>
> All unquoted identifiers are assumed by PostgreSQL to be lower case by
> default. This means
> - SELECT MY_COLUMN FROM my_table
> - SELECT my_column FROM my_table
> - SELECT my_column as MY_COLUMN FROM
Hello,
All unquoted identifiers are assumed by PostgreSQL to be lower case by
default. This means
- SELECT MY_COLUMN FROM my_table
- SELECT my_column FROM my_table
- SELECT my_column as MY_COLUMN FROM my_table
All refer to my_column and has column name in lowercase as my_column.
If the aliases ar
Hello Everyone,
I am using postgres 9.2 and when executing function dblink facing a fatal
error while trying to execute dblink_connect as follows:
* SELECT * FROM dblink_connect('host=127.0.0.1 port=5432 dbname=postgres
password=test')*
*ERROR*: could not establish connection DETAIL: FATA
Hello Again,
Using dblink and now am facing a fatal error while tryinf to execute
dblink_connect as follows:
SELECT *
FROM dblink_connect('host=127.0.0.1 port=5432 dbname=postgres
password=test')
ERROR: could not establish connection
DETAIL: FATAL: password authentication failed for user "NET
Am looking for pointers related to cross-database queries?
Thanks in advance!
On Tue, Feb 5, 2013 at 10:42 PM, Dev Kumkar wrote:
> Hello everyone,
>
> Please can you point me to the contrib/dblink package links.
>
> What am actually looking for is query multiple database located
Hello everyone,
Please can you point me to the contrib/dblink package links.
What am actually looking for is query multiple database located on
different machines. Is there any documentation for same which tells the
metadata steps?
Existing archive link if exists please can you point me same.
Re
14 matches
Mail list logo
