| From: | De Leeuw Guy <G(dot)De_Leeuw(at)eurofer(dot)be> | 
|---|---|
| To: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> | 
| Cc: | pgsql-admin(at)postgresql(dot)org | 
| Subject: | Re: cache problem (v2) | 
| Date: | 2007-07-17 15:49:15 | 
| Message-ID: | 469CE4FB.9080403@eurofer.be | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-admin | 
> Yes.  _Everything_ is in a transaction in PostgreSQL.  If you don't
> explicitly do BEGIN. . .COMMIT, then the system does it implicitly
> for each statement.
>   
>> if yes each time my trigger select a data
>> and update then the value returned by the read are the value before the
>> transaction. It's true ? if yes my question are : also in the same
>> transaction (like my trigger) ?
>>     
>
> Your trigger function runs inside the transaction of the calling
> statement, unless you have explicitly started a transaction. 
>   
Not possible from a trigger
> I'm starting to get the impression you have a misunderstanding of how
> PostgreSQL works.  I think you maybe need to spend some more time
> with the manual.  If you find the English version puzzling, you can
> also work in French (at http://docs.postgresqlfr.org/) or German (I
> see a translation at
> http://www.postgresql.org/docs/books/pghandbuch.html.de; I dunno if
> there's a more recent one).  Sorry, AFAIK there isn't one in Dutch.
>   
Yes true, It's my first step with postgres but also with a relationnal
database.
But I'm sure that with COPY the data are not correctly updated and
if I edit the file loaded by the COPY command and adapt it with each
line with a command INSERT all work fine.
Guy
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2007-07-17 16:23:06 | Re: cache problem (v2) | 
| Previous Message | Abraham, Danny | 2007-07-17 15:45:29 | plpgsql debugger |