Richard Broersma Jr <[EMAIL PROTECTED]> writes:
> --- "Luiz K. Matsumura" <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
