Re: Missing can't-assign-to-constant checks in plpgsql - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: Missing can't-assign-to-constant checks in plpgsql
Date
Msg-id CAFj8pRDsT6qG0oiVn6zac-+H5zjTZ6TRRZOmK_g-=FUVzP5Wgg@mail.gmail.com
Whole thread Raw
In response to Re: Missing can't-assign-to-constant checks in plpgsql  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Hi


Regardless of which way we handle that point, I'm inclined to
change this only in HEAD.  Probably people wouldn't thank us
for making the back branches more strict.

+1

I can implement these checks in plpgsql_check. So possible issues can be detected and fixed on older versions by using plpgsql_check.

new related checks are implemented on plpgsql_check 2.1.4

Regards

Pavel
 

Regards

Pavel


                        regards, tom lane

PS: I didn't do it here, but I'm kind of tempted to pull out
all the cursor-related tests in plpgsql.sql and move them to
a new test file under src/pl/plpgsql/src/sql/.  They look
pretty self-contained, and I doubt they're worth keeping in
the core tests.

pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: testclient.exe installed under MSVC
Next
From: Daniele Varrazzo
Date:
Subject: Libpq single-row mode slowness