Message-ID: <4427F7D3.3000103@gmail.com>
Date: Mon, 27 Mar 2006 16:33:55 +0200
From: Wiebe Cazemier <halfgaar@gmail.com>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20060225)
MIME-Version: 1.0
To: pgsql-sql@postgresql.org
Subject: unique names in variables and columns in plsql functions
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigB156D5C2C2843E68716DB5CF"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigB156D5C2C2843E68716DB5CF
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi,

In a plpgsl function, consider the following excerpt:

DECLARE
  provider_id INTEGER;
BEGIN
  provider_id := (SELECT provider_id FROM investment_products WHERE id =
my_new.investment_product_id);
END;

After a lot of trouble, I found out this line doesn't work correctly
with the variable name as it is. It doesn't give an error or anything,
it just retrieves some wrong value (probably NULL). When I change the
variable name to anything other than "provider_id", it works OK.

I was somewhat surprised to discover this. Can't Postgres determine that
the provider_id in the SELECT statement is not the same one as the variable?

--------------enigB156D5C2C2843E68716DB5CF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEJ/fTMHkUjYo9d9ARAlCVAJ0VzfNAqdAfTpZgQi7glcvEUIH/FwCePIDq
LCpGTp9HiZNdKiSpHdLsDE4=
=Je3F
-----END PGP SIGNATURE-----

--------------enigB156D5C2C2843E68716DB5CF--