> > No, it does not match what I'm seeing. To check, I dropped my test
> > table and function, exited psql, started psql, and ran the script I
> > originally posted. I still get the same results. If I had to guess, this
> > seems more like a Postgres to plpython conversion problem than a
> > ca
Arthur Ward <[EMAIL PROTECTED]> writes:
> No, it does not match what I'm seeing. To check, I dropped my test
> table and function, exited psql, started psql, and ran the script I
> originally posted. I still get the same results. If I had to guess, this
> seems more like a Postgres to plpython c
> There is a known bug with applying the same plpython trigger function to
> multiple tables that have different rowtypes --- the rowtype info gets
> cached for the first table the function is used with in a session, and
> then inappropriately reused with the other tables. Does this seem to
> desc
Arthur Ward <[EMAIL PROTECTED]> writes:
> I'm running "PostgreSQL 7.3.3 on i686-pc-linux-gnu, compiled by
> GCC gcc (GCC) 3.2.2", and seeing a problem in trigger functions
> written in plpython.
There is a known bug with applying the same plpython trigger function to
multiple tables that have di
I'm running "PostgreSQL 7.3.3 on i686-pc-linux-gnu, compiled by
GCC gcc (GCC) 3.2.2", and seeing a problem in trigger functions
written in plpython. This also happens in 7.3.2; I upgraded this
morning to see if the problem was already fixed. For fields of type
char, when a plpython trigger is c
