"Arthur Ward" <[EMAIL PROTECTED]> writes:
> I have a table with a plpython trigger defined on it in 7.3.4. I've
> dropped a column from that table, and now I cannot get a plpython trigger
> to run at all on that table.
Would you try the attached patch?
regards, tom lane
*
I have a table with a plpython trigger defined on it in 7.3.4. I've
dropped a column from that table, and now I cannot get a plpython trigger
to run at all on that table. I've dropped both the trigger and function
and recreated them from scratch (not using "create or replace"), and I
still get the
"Tom Lane" <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] (Payman) writes:
> > Hey tom and your PowerBook ???
>
> I had it back for a day, and it went belly up again :-(
Look at this then
http://www.waveworks.net/mac.html
:-)
Regards
Gaetano Mendola
---(end of broadca
"Matthew Cooper" <[EMAIL PROTECTED]> writes:
> Attached is the UTF-8 encoded sql file in case it got messed up in the mail
> transfer.
Ah, no doubt it did.
This works fine for me, using either 7.3.4 or CVS tip. Are you sure
that the system knows your client-side encoding is supposed to be UTF8?
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
> Sent: Wednesday, September 10, 2003 6:42 PM
> To: Christoph Jaeger
> Cc: [EMAIL PROTECTED]
> Subject: Re: [BUGS] Foreign key constraint still active after
> table row removed
>
>
> "Chris
