diff options
author | Bruce Momjian | 2002-09-12 00:24:10 +0000 |
---|---|---|
committer | Bruce Momjian | 2002-09-12 00:24:10 +0000 |
commit | b3f52320f6cb8374f3db5397e63b82f595c90681 (patch) | |
tree | 838a5b8f866b54fce0996e9b7a433bc10a119b3c /contrib/cube/cube.c | |
parent | 81186865fec2e39a6a66e9435b32d7048c03dd32 (diff) |
> Sean Chittenden <sean@chittenden.org> writes:
>
>>::sigh:: Is it me or does it look like all
>>of pl/pgsql is schema un-aware (ie, all of the declarations). -sc
>
>
> Yeah. The group of routines parse_word, parse_dblword, etc that are
> called by the lexer certainly all need work. There are some
> definitional issues to think about, too --- plpgsql presently relies on
> the number of names to give it some idea of what to look for, and those
> rules are probably all toast now. Please come up with a sketch of what
> you think the behavior should be before you start hacking code.
Attached is a diff -c format proposal to fix this. I've also attached a short
test script. Seems to work OK and passes all regression tests.
Here's a breakdown of how I understand plpgsql's "Special word rules" -- I
think it illustrates the behavior reasonably well. New functions added by this
patch are plpgsql_parse_tripwordtype and plpgsql_parse_dblwordrowtype:
Joe Conway
Diffstat (limited to 'contrib/cube/cube.c')
0 files changed, 0 insertions, 0 deletions