Bug or Feature - plpgsql odity
От | Uwe C. Schroeder |
---|---|
Тема | Bug or Feature - plpgsql odity |
Дата | |
Msg-id | 200311301946.51411.uwe@oss4u.com обсуждение исходный текст |
Ответы |
Re: Bug or Feature - plpgsql odity
|
Список | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, following odity: I have a table "quote". In a stored proc I do a rquote quote%ROWTYPE; SELECT INTO rquote * FROM quote WHERE .....(some clause resulting in one record) Fine so far. Now I manually add a column to the table (via psql). After that I do a vacuum full analyze - just to make sure. BUT: The above SELECT fails to retrieve a value for the new column. It will always return NULL, even after I stored the procedure again (using the create or replace syntax). Values for all other columns are OK. If I declare the rquote variable as type RECORD everything works as expected. Is the %ROWTYPE" cached somewhere ? Is that intentional ? Accessing rquote.newcolumn doesn't raise an exception, but the value is NULL Running 7.3.2 on linux. UC - -- Open Source Solutions 4U, LLC 2570 Fleetwood Drive Phone: +1 650 872 2425 San Bruno, CA 94066 Cell: +1 650 302 2405 United States Fax: +1 650 872 2417 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/yrmrjqGXBvRToM4RAm1EAJoCQGXhYGhdAGexNX5QaHI8MtAGAACgjWjC 3y04n9FTpEeX8FxEgkEU5Cw= =okfE -----END PGP SIGNATURE-----
В списке pgsql-general по дате отправления: