Re: [HACKERS] Parser doesn't grok unqualified array element

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Parser doesn't grok unqualified array element
Date: 1999-03-29 17:31:53
Message-ID: 36FFB909.7D512993@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Has this come up before? 6.4.2 and current sources both have
> this problem:
> select count(*) from pg_proc where pg_proc.proargtypes[0] = 701;
> works, but
> select count(*) from pg_proc where proargtypes[0] = 701;
> fails with
> ERROR: Unable to locate type name 'proargtypes' in catalog
>
> The grammar doesn't seem to have a case that allows for a subscripted
> attribute name without a relation name in front of it.
> It looks like fixing this might be as easy as making the "ColId"
> cases in a_expr, b_expr, possibly other places include an
> opt_indirection item like columnElem does. But maybe there's
> more to it than meets the eye?

It has been reported, and is probably on the ToDo list as something. I
have been carrying it on my personal ToDo for a while, just to make
sure it doesn't get lost.

I would try your solution if I were fixing it, which I'm not yet. Go
fer it dude!

- Tom

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Vazsonyi Peter[ke] 1999-03-29 17:32:43 Re: [HACKERS] NULL handling question
Previous Message Thomas Lockhart 1999-03-29 17:28:34 Re: [HACKERS] Speedup idea: avoid using SQL procedures as aliases