Re: Trigger (Transaction related)

From: Roman Neuhauser <neuhauser(at)sigpipe(dot)cz>
To: Harpreet Dhaliwal <harpreet(dot)dhaliwal01(at)gmail(dot)com>
Cc: Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-general(at)postgresql(dot)org
Subject: Re: Trigger (Transaction related)
Date: 2006-09-01 09:28:56
Message-ID: 20060901092856.GA99468@dagan.sigpipe.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

# harpreet(dot)dhaliwal01(at)gmail(dot)com / 2006-09-01 03:19:03 -0400:
> If that is the case then why does it throw error in one on the insert
> queries in the shared object written in SPI without inserting the row on the
> table on which record is inserted.
>
> Follwing query in the shared object throws an error.
>
>
> INSERT INTO headers (id, header_content) VALUES (1, SELECT raw_email FROM
> parser WHERE id = 1)
>
> Error is
> ERROR: syntax error at or near "SELECT" at character 53

Because there's a syntax error.

test=# INSERT INTO headers (id, header_content) VALUES (1, SELECT raw_email FROM parser WHERE id = 1);
ERROR: syntax error at or near "SELECT" at character 53
LINE 1: ...SERT INTO headers (id, header_content) VALUES (1, SELECT raw...
^
test=# INSERT INTO headers (id, header_content) VALUES (1, (SELECT raw_email FROM parser WHERE id = 1));
ERROR: relation "headers" does not exist
test=#

> Regardless the error in the shared object, why doesn't it insert the
> row in the table on which AFTER INSERT trigger is written?

Perhaps you should verify the syntax of your queries in a less
demanding environment, like psql, first.

--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you weren't THERE. http://bash.org/?255991

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message nhrcommu 2006-09-01 10:03:09 Training (from Thought provoking...)
Previous Message Csaba Nagy 2006-09-01 09:25:30 Re: Strange error related to temporary tables