From: | Laura McCord <mccordl(at)southwestern(dot)edu> |
---|---|
To: | |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Having a problem with my stored procedure |
Date: | 2007-02-13 19:35:36 |
Message-ID: | 45D21308.9070503@southwestern.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
Thanks,
Laura
Tom Lane wrote:
> Laura McCord <mccordl(at)southwestern(dot)edu> writes:
>
>> I tried doing two different triggers as you suggested but I kept getting
>> an error stating:
>>
>
>
>> psql:archive_news_articles.sql:75: ERROR: trigger "archive_articles"
>> for relation "news_content" already exists
>> psql:archive_news_articles.sql:80: ERROR: trigger "update_archives" for
>> relation "news_content" already exists
>>
>
>
>> So, I thought perhaps it couldn't be done.
>>
>
> You need to pick different names for the triggers ... or if you're
> trying to replace an existing trigger definition, you need to DROP it first.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Dhaval Shah | 2007-02-13 19:39:35 | Using PITR for creating Hot Standby |
Previous Message | Tom Lane | 2007-02-13 19:23:58 | Re: Having a problem with my stored procedure |