Re: [pgadmin-hackers] error rename column
> -Original Message- > From: frank_lupo [mailto:[EMAIL PROTECTED]] > Sent: 17 July 2002 07:55 > To: pgadmin-hackers > Subject: [pgadmin-hackers] error rename column > > > I have a column name is 'desc' . > If you rename a clomun using form pgadmin2 error parsing. > Desc is a keyword reserved. 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? Regards, Dave. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
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) John ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [pgadmin-hackers] error rename column
> -Original Message- > From: John McCawley [mailto:[EMAIL PROTECTED]] > 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. ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
