From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Michael J Schout <mschout(at)gkg(dot)net> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] 6.4 and reserved word USER... |
Date: | 1998-10-29 04:37:22 |
Message-ID: | Pine.BSF.4.05.9810290037110.28793-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Didn't we make that change for v6.3.2? *raised eyebrow*
On Wed, 28 Oct 1998, Michael J Schout wrote:
> Hi.
>
> I have not followed hackers regularly, so im sure this has probably been
> asked before. Anyways, I tried the 6.4 beta 3 today, and noticed that
> the
> word "USER" has been reserved now. Since I have an app that uses a
> column
> named "user" I went into backend/parser/gram.y and added a line like:
>
> | USER { $$ = "user" }
>
> into that file so that USER would be accepted.
>
> However, I noticed that this breaks a lot of queries :). Apparently
> doing a
> "SELECT user" now returns your username. So in order to make my queries
> work
> I would have to do "SELECT table.user FROM table....". If there is no
> other
> way around it, Ill probably just have to rename the colunm and track
> down all
> references to it in my application (ugh :().
>
> SO my question is this: Is there anything else that could be done to
> make
> this work? Or will we break the "SELECT USER" usefulness by doing
> something
> like this? Im guessing its probably not going to be possible :) But
> though
> I would ask those a little more familiar with the source tree than me
> since
> I just started looking at at now :)
>
> Mike
>
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 1998-10-29 04:39:29 | Re: [HACKERS] Another bug in pg_operator.h |
Previous Message | The Hermit Hacker | 1998-10-29 04:36:22 | Re: [HACKERS] Another bug in pg_operator.h |