Re: typoed column name, but postgres didn't grump

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: typoed column name, but postgres didn't grump
Date: 2010-10-29 17:48:18
Message-ID: 4480.1288374498@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-performance

Jon Nelson <jnelson+pgsql(at)jamponi(dot)net> writes:
> Initially, I mis-typed the query, and one of the columns specified in
> the query doesn't exist, however the query ran nonetheless.

> The actual query:
> select gid from t2, t3 where t2.name = t3.name and t3.scope = 'city'
> and t3.hierarchy = 'STANDARD' and t2.adiv = t3.adiv limit 1 ;
> However, there *is* no column 'name' in table 't2'.

This is the old automatic-cast-from-record-to-text-string issue,
ie it treats this like "(t2.*)::name".

We've been over this a few times before, but it's not clear that
we can make this throw an error without introducing unpleasant
asymmetry into the casting behavior, as in you couldn't get the
cast when you did want it.

BTW this seems pretty far off-topic for pgsql-performance.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2010-10-29 17:56:23 Re: What happened to SSL_CIPHERS?
Previous Message Magnus Hagander 2010-10-29 17:39:04 Re: What happened to SSL_CIPHERS?

Browse pgsql-performance by date

  From Date Subject
Next Message Robert Haas 2010-10-29 18:13:31 Fwd: failure notice
Previous Message Kevin Grittner 2010-10-29 17:18:20 Re: MVCC and Implications for (Near) Real-Time Application