From: | Douglas McNaught <doug(at)mcnaught(dot)org> |
---|---|
To: | David Rio Deiros <driodeiros(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: C trigger using system(3) to execute a php script |
Date: | 2006-02-16 19:24:06 |
Message-ID: | 87lkwb9kfd.fsf@suzuka.mcnaught.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
David Rio Deiros <driodeiros(at)gmail(dot)com> writes:
> Then, I wanted to run the full php script from the trigger. I tried
> the script manually, form the shell, and it worked perfectly. Notice
> that the script doesn't generate any stdin/stdout output. So I changed
> the system(3) parameter to call my php script instead of the test one.
> I tried it and it didn't work. The php script doesn't perform the
> modifications it suppose to in the database.
>
> The php script is about 150 lines long and performs like 5 or 6 sql
> queries/inserts against the database.
Why would you do it that way? The queries/inserts won't be rolled
back if the transaction containing the trigger aborts (because they'd
be done in a separate session). Why not just do your queries from C
using the SPI interface?
-Doug
From | Date | Subject | |
---|---|---|---|
Next Message | David Rio Deiros | 2006-02-16 20:16:22 | Re: C trigger using system(3) to execute a php script |
Previous Message | jim_bowery | 2006-02-16 19:23:52 | Ident authentication failed without su to user |