I did check with customer support (they are actual developers of the
system not middle men) and they said there aren't any triggers in the db
structure so it's safe for me to include triggers. So, that helps me
feel reassured because you had a good point. So more than likely, it was
my error and I
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
> <[EMAIL PROTECTED]> wrote:
>
>> He
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 <[EMAIL PROTECTED]> writes:
>
>> I tried doing two different triggers as you su
t's a long story.
-Laura
Laura McCord wrote:
> 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
e
> rather than copying the values first into the temporaries and then
> from the temporaries into their final destination?
>
> HTH
>
> Ted
>
> - Original Message -
> *From:* William Leite Araújo <mailto:[EMAIL PROTECTED]>
> *To:* Laura McCord <
To make a long story short, I am archiving data from an original table
to a table I created. This is a third party web application that I am
doing this with, so I can't revise the structure/code of this
application. With this said, if the original table goes through an
insert or update action I wan
