Re: Having a problem with my stored procedure

From: Laura McCord <mccordl(at)southwestern(dot)edu>
To: Alan Hodgson <ahodgson(at)simkin(dot)ca>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Having a problem with my stored procedure
Date: 2007-02-13 19:51:01
Message-ID: 45D216A5.9040806@southwestern.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ok, I think I am starting to put two-and-two together.... based on your
thread and Ted's thread, I just realized that OLD. and NEW. are keywords
in postgres.

Alan Hodgson wrote:
> On Tuesday 13 February 2007 11:35, Laura McCord
> <mccordl(at)southwestern(dot)edu> wrote:
>
>> Here is a question that I am stumped on:
>>
>> Does postgres even recognize last_inserted() as mysql does? I notice
>> that the function fails on that line.
>>
>>
>
> Not, that's just a MySQL function. You could, however, look for the
> last value of the sequence generator for the table's primary key, which
> should be (but may not always be) equivalent.
>
> However, you are doing far more work than necessary getting the
> inserted/updated data; you can just access it through the OLD. and NEW.
> records already provided to the trigger.
>
> http://www.postgresql.org/docs/8.2/interactive/plpgsql-trigger.html
>
>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message gustavo halperin 2007-02-13 19:52:05 SEQUENCE primary key
Previous Message Alan Hodgson 2007-02-13 19:45:52 Re: Having a problem with my stored procedure