Re: [GENERAL] Triggers not working

2008-09-22 Thread Dale Harris
row that appears there, even rows added via a child table. It would mean that any new table that inherits the parent table, in my case Entity, would automatically have the global trigger I want enforced. Nice enhancement :) Regards, Dale Harris. -Original Message- From: Tom Lane [mailto

Re: [GENERAL] Triggers not working

2008-09-22 Thread Dale Harris
Hi Tom, The trigger trAccountUpdate got called, but why didn't the trigger trEntityUpdate get called? Regards, Dale Harris. -Original Message- From: Tom Lane [mailto:[EMAIL PROTECTED] Sent: Monday, 22 September 2008 22:22 To: Dale Harris Cc: pgsql-general@postgresql.org Subjec

[GENERAL] Triggers not working

2008-09-21 Thread Dale Harris
Hi, I'm running PostgreSQL 8.3.3 and I'm having trouble with triggers not always working. I have the following tables and functions as documented below. My problem is that if I perform an update on the Entity table and modify the Code field, why doesn't the trigger for the Entity table execut

Re: [GENERAL] can't get UPDATE ... RETURNING ... INTO ... to compile successfully

2008-08-19 Thread Dale Harris
cript and the WHERE clause selects an unique record. Therefore only 1 value should ever be returned. The point is that I don't even get that far as the script fails to compile due to the INTO clause. Regards, Dale. -Original Message- From: Klint Gore [mailto:[EMAIL

Re: [GENERAL] can't get UPDATE ... RETURNING ... INTO ... to compile successfully

2008-08-19 Thread Dale Harris
Hi All, In the following documentation it advises that the UPDATE statement should be able to return a value into a variable in plpgsql. http://www.postgresql.org/docs/8.3/static/plpgsql-statements.html It works for the INSERT command, but not UPDATE. For the INSERT command, it makes my code lo

Re: [GENERAL] cannot use result of (insert .. returning)

2008-08-14 Thread Dale Harris
Hi Pavel, Thank you for your reply, but in this case the “INSERT INTO ... RETURNING field,... INTO STRICT variable,...;” is what works best for me currently. Regards, Dale Harris -Original Message- From: Pavel Stehule [mailto:[EMAIL PROTECTED] Sent: Thursday, 14 August

Re: [GENERAL] cannot use result of (insert .. returning)

2008-08-14 Thread Dale Harris
I've found my solution as in the help file under "RETURNING INTO". It would be nice if this was referenced on the INSERT documentation. Dale From: [EMAIL PROTECTED] Sent: Thursday, 14 August 2008 15:32 To: pgsql-general@postgresql.org Subject: [GENERAL] cannot use result of (insert .. ret

[GENERAL] cannot use result of (insert .. returning)

2008-08-13 Thread Dale Harris
Hello, I'm having the same issues as dvs had in message thread http://archives.postgresql.org/pgsql-general/2008-05/msg01117.php as I want to be able to use the result from an INSERT INTO table(...) VALUES(...) RETURNING new_row_ID. I would ideally like to be able to capture the RETURNING v