"Mark Reid" <[EMAIL PROTECTED]> writes:
> If a column is added, dropped, then re-added (all within a transaction), a
> plpython trigger function loses track of the column and throws an error when
> trying to access it. Here is the best minimal test case I could come up
> with:
The cases you are s
The following bug has been logged online:
Bug reference: 3848
Logged by: Ion
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3
Operating system: Windows XP SP2
Description:function pg_catalog.substring(date, integer, integer)
does not exist
Details:
Hello,
I
On Tue, Jan 01, 2008 at 08:11:01PM +, Ion wrote:
> Email address: [EMAIL PROTECTED]
lets hope Ion is subscribed! :)
> I tested PostgreSQL 8.3 beta4 with tinyerp and I have this problem:
> pg_catalog.substring(date, integer, integer) does not exist
This is most likely a bug in tinyerp. s
Sam Mason <[EMAIL PROTECTED]> writes:
> I've just downloaded the source of tinyerp and had a look though and
> this practice seems pretty endemic. They should really be using
> to_char(date_exp, '-MM')
> instead of
> substring(date_exp FOR 7)
> in all their queries.
Or at least explicitly
On Tue, Jan 01, 2008 at 04:29:47PM -0500, Tom Lane wrote:
> Sam Mason <[EMAIL PROTECTED]> writes:
> > I've just downloaded the source of tinyerp and had a look though and
> > this practice seems pretty endemic. They should really be using
> > to_char(date_exp, '-MM')
> > instead of
> > sub
The trigger function does not recognize the "test4" column the second time
it is added - the update throws an error.
On Jan 1, 2008 11:17 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Mark Reid" <[EMAIL PROTECTED]> writes:
> > If a column is added, dropped, then re-added (all within a transaction),
This has been saved for the 8.4 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Pedro Gimeno wrote:
> Tom Lane wrote:
>
> > "Kevin Grittner" <[EMAIL PROTECTED]> writes:
> >> That said, bringing Po
"Mark Reid" <[EMAIL PROTECTED]> writes:
> The trigger function does not recognize the "test4" column the second time
> it is added - the update throws an error.
Try this patch:
http://archives.postgresql.org/pgsql-committers/2008-01/msg00016.php
regards, tom lane
