Hi,
I am upgrading a system from postgresql 8.4.8 (fedora 13 x64) to postgresql
9.0.5 (fedora 15 x64). As I build a database I've noticed that the following
works on 8.4.8 but does not work on 9.0.5. Can someone tell me why this is not
legal syntax in 9.0.5 but is legal in 8.4.8 please:
Hello
http://developer.postgresql.org/pgdocs/postgres/release-9-0.html
PL/pgSQL no longer allows variable names that match certain reserved
words (Tom Lane)
use double quotes
rec.open = 32;
Regards
Pavel Stehule
2011/11/23 Chris McDonald chrisjonmcdon...@gmail.com:
Hi,
I am upgrading a
Chris McDonald chrisjonmcdon...@gmail.com writes:
Hi, I am upgrading a system from postgresql 8.4.8 (fedora 13 x64) to
postgresql 9.0.5 (fedora 15 x64). As I build a database I've noticed
that the following works on 8.4.8 but does not work on 9.0.5. Can
someone tell me why this is not legal
Chris McDonald chrisjonmcdon...@gmail.com writes:
Hi, I am upgrading a system from postgresql 8.4.8 (fedora 13 x64) to
postgresql 9.0.5 (fedora 15 x64). As I build a database I've noticed
that the following works on 8.4.8 but does not work on 9.0.5. Can
someone tell me why this is not legal
Jerry Sievers gsiever...@comcast.net writes:
Hmmm, I do not see that open is a reserved word but the PL must be
treating it special somehow.
plpgsql has a different list of reserved words than the main SQL grammar
does. I don't think we explicitly document it anywhere, but pretty much
any
OK, I see it is the term open which fails the syntax checker - I guessed this
might be because open is a reserved word but
http://www.postgresql.org/docs/9.0/interactive/sql-keywords-appendix.html does
not indicate whether open is either reserved or not in postgresql.
Checking 8.4 doco,
On Wednesday, November 23, 2011 11:43:04 am Chris McDonald wrote:
OK, I see it is the term open which fails the syntax checker - I guessed
this might be because open is a reserved word but
http://www.postgresql.org/docs/9.0/interactive/sql-keywords-appendix.html
does not indicate whether open
Chris McDonald chrisjonmcdon...@gmail.com writes:
Still interested in a definitive answer, but the fix for me appears to be
simply to change the word open to something else.
Well, if you want a definitive answer, you can consult the list of
plpgsql reserved words here:
