Re: [SQL] trigger on DELETE

2001-07-11 Thread Kristis Makris
> Ok, the function works only with a trigger that is defined as ON INSERT > OR UPDATE. If I try to define a trigger for ON DELETE and then delete a > row from the table, there is nothing in the 'NEW' variable to return. I > get an error message. If I define the function to return NULL, 0, or >

[SQL] Re: [BUGS] ERROR: deferredTriggerGetPreviousEvent: event for tuple(0,9) not found

2001-07-11 Thread Kristis Makris
On 11 Jul 2001 13:56:58 -0400, Tom Lane wrote: > > but if I want to clear the valuntil completely, how should I issue the > > ALTER USER statement? > > Offhand I don't believe ALTER USER can do that. Feel free to submit > a patch ;-). This seems to have a similar effect: ALTER USER test VALID

[SQL] Re: [BUGS] ERROR: deferredTriggerGetPreviousEvent: event for tuple(0,9) not found

2001-07-11 Thread Kristis Makris
> So that raises this from an unimplemented feature to a real bug, or at > least higher priority in my eyes. You can't do a CREATE/ALTER USER > followed by an UPDATE on pg_shadow in a single transaction: I'm glad I could be of some help. I don't know if the following means anything to you (or t

[SQL] ERROR: Procedures cannot take more than 16 arguments

2001-07-10 Thread Kristis Makris
Hello all, Using PostgreSQL 7.1.2 on i686-pc-linux-gnu, compiled by GCC egcs-2.91.66, I attempted to create a plpgsql function that takes 17 arguments and I received the error: ERROR: Procedures cannot take more than 16 arguments Can this limit be increased by manipulating some variable in th