Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id F1C029FB538 for ; Tue, 17 Jul 2007 12:49:48 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 76535-03 for ; Tue, 17 Jul 2007 12:49:32 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from BRUBLUmx12.mactelecom.net (BRUBLUmx12.mactelecom.net [217.64.240.4]) by postgresql.org (Postfix) with ESMTP id 157829FB2C1 for ; Tue, 17 Jul 2007 12:49:37 -0300 (ADT) Received: from smtp.eurofer.be (217.64.254.218.mactelecom.net [217.64.254.218]) by BRUBLUmx12.mactelecom.net (Postfix) with ESMTP id E3E438380B1; Tue, 17 Jul 2007 17:49:36 +0200 (CEST) Received: from ip-80-236-220-100.dsl.scarlet.be ([80.236.220.100] helo=[192.168.1.105]) by smtp.eurofer.be with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1IApIZ-0002V5-W4; Tue, 17 Jul 2007 17:49:36 +0200 Message-ID: <469CE4FB.9080403@eurofer.be> Date: Tue, 17 Jul 2007 17:49:15 +0200 From: De Leeuw Guy User-Agent: IceDove 1.5.0.10 (X11/20070329) MIME-Version: 1.0 To: Andrew Sullivan CC: pgsql-admin@postgresql.org References: <469B4927.9030604@eurofer.be> <20070716170957.GV18049@phlogiston.dyndns.org> <469BAF1D.8030108@eurofer.be> <20070716184837.GB18049@phlogiston.dyndns.org> <469BD389.4030606@eurofer.be> <20070716203641.GF18049@phlogiston.dyndns.org> <469C5AC4.7040903@eurofer.be> <20070717152848.GD21688@phlogiston.dyndns.org> In-Reply-To: <20070717152848.GD21688@phlogiston.dyndns.org> X-Enigmail-Version: 0.94.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam_score: -3.8 X-SA-Exim-Connect-IP: 80.236.220.100 X-SA-Exim-Mail-From: G.De_Leeuw@eurofer.be Subject: Re: cache problem (v2) X-SA-Exim-Scanned: Yes (on smtp.eurofer.be) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/178 X-Sequence-Number: 26159 > 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