Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 37273 invoked by uid 500); 14 May 2003 05:18:58 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 37252 invoked from network); 14 May 2003 05:18:57 -0000 Received: from vamana-60.cablenet.com.ni (HELO ags01.agsoftware.dnsalias.com) (216.6.48.60) by daedalus.apache.org with SMTP; 14 May 2003 05:18:57 -0000 Received: from ags01.agsoftware.dnsalias.com (localhost [127.0.0.1]) by ags01.agsoftware.dnsalias.com (8.12.8/8.12.5) with ESMTP id h4E5J7oJ010957 for ; Tue, 13 May 2003 23:19:07 -0600 Received: (from apache@localhost) by ags01.agsoftware.dnsalias.com (8.12.8/8.12.8/Submit) id h4E5J7gL010955; Tue, 13 May 2003 23:19:07 -0600 X-Authentication-Warning: ags01.agsoftware.dnsalias.com: apache set sender to agallardo@agsoftware.dnsalias.com using -f Received: from 10.0.0.5 (SquirrelMail authenticated user agallardo) by ags01.agsoftware.dnsalias.com with HTTP; Tue, 13 May 2003 23:19:07 -0600 (CST) Message-ID: <33485.10.0.0.5.1052889547.squirrel@ags01.agsoftware.dnsalias.com> Date: Tue, 13 May 2003 23:19:07 -0600 (CST) Subject: Re: transactions in the SQLTransformer From: "Antonio Gallardo" To: In-Reply-To: <3EC1D07F.3090703@dotech.com> References: <3EC1D07F.3090703@dotech.com> X-Priority: 3 Importance: Normal X-Mailer: SquirrelMail (version 1.2.11) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi: I am not using SQLTransformer, but using Modular Database Action you get it. More info at: http://wiki.cocoondev.org/Wiki.jsp?page=ModularDatabaseActions Best Regards, Antonio Gallardo David Kavanagh dijo: > I need to a sequence of sql commands and be able to rollback if anyone > fails. Does the SQLTransformer support transactions? I looked through > the SQLTransformer code to see what this might take to add. Easy to add > the parameter to turn the transaction processing on. The biggest problem > I saw was that connections are used for one query only, then closed. > I'd have to keep the connection open for the duration of query > processing. I can think of ways to do this, but are there any > implications I should be concerned about? > If done right, I could see giving this feature back. Has there been any > demand? > > David