From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "John McCawley" <jmccawley(at)worleyco(dot)com> |
Cc: | "pgadmin-hackers" <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: error rename column |
Date: | 2002-07-17 13:11:55 |
Message-ID: | D85C66DA59BA044EB96AB9683819CF61137F72@dogbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
> -----Original Message-----
> From: John McCawley [mailto:jmccawley(at)worleyco(dot)com]
> Sent: 17 July 2002 16:02
> To: Dave Page
> Cc: pgadmin-hackers
> Subject: Re: [pgadmin-hackers] error rename column
>
>
> Dave Page wrote:
>
> >The only way I can think to prevent this is to include lists of
> >reserved words in pgAdmin - something I didn't want to do as
> they can
> >require maintenance. Anyone have any other ideas?
> >
> >
>
> Is it a VB reserved word, or SQL Reserved word as in 'ORDER
> BY foo DESC'? (I assume SQL, but wanted to clarify)
SQL, the only (as far as I'm aware) concept of reserved words in VB is
in function/variable naming. The problem is, PostgreSQL has a number of
lists of reserved words (for various levels of 'reserved') which change
from release to release - something that would require careful
monitoring.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | John McCawley | 2002-07-17 15:01:52 | Re: error rename column |
Previous Message | Dave Page | 2002-07-17 08:36:24 | Re: error rename column |