From: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard Broersma Jr <rabroersma@yahoo.com>
Cc: Luiz K. Matsumura <luiz@planit.com.br>
Cc: pgsql-sql@postgresql.org
Subject: Re: Cast on character columns in views
Date: Tue, 04 Sep 2007 11:03:08 -0400
Message-ID: <25051.1188918188@sss.pgh.pa.us> (raw)
In-Reply-To: <108933.2667.qm@web31807.mail.mud.yahoo.com>
References: <108933.2667.qm@web31807.mail.mud.yahoo.com>
Richard Broersma Jr <rabroersma@yahoo.com> writes:
> --- "Luiz K. Matsumura" <luiz@planit.com.br> wrote:
>> But when I open a query tool window and do:
>> SELECT * FROM view1;
>> Now, again type1 column returns as bpchar.
> This might be a good question to ask on the PGAdmin mailing list or even try using the latest
> version of PGAdmin. Perhaps this is something that PGAdmin is doing rather than postgresql.
The seeming ordering dependency certainly sounds like it might be a
client-side bug --- something failing to keep straight which typmod goes
with which column, maybe?
There are some backend-side issues with simply not being able to tell
the difference between null::bpchar and null::char(3) ... but for
any given view definition, it's pretty hard to see how the order of
selecting the columns would matter. A client-side bug seems a bit
more likely.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, rabroersma@yahoo.com, luiz@planit.com.br
Subject: Re: Cast on character columns in views
In-Reply-To: <25051.1188918188@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox