cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Fagerstrom <dani...@nada.kth.se>
Subject Re: SQL Editor
Date Mon, 03 Feb 2003 16:43:13 GMT
Jeremy Quinn wrote:
> Hi Guys
> 
> I am looking into implementing a forms-based editor for a complex set of 
> inter-related SQL Tables (with lots of gruesome link tables etc.).
> 
> What is currently considered the best technique to be using in Cocoon 
> right now?
> 
> XMLForm (we don't use Beans)
> OriginalDBActions (obsolete ? )
> ModularDBActions (Actions are not liked by many)
> SQL Inserts/Updates using SQLTransformer (maybe not capable of the job 
> due to complexities of the multiple Table updating required ? )

We are using the SQLTransformer for all insert/updates etc on the 
company that I work for. For more complex update actions involving 
transactions the current implementation is not usable as it opens a new 
connection for each execute-query element. I have written a patch that 
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16718 that solves that 
problem.

/Daniel Fagerstrom

> SQL Inserts/Updates using ESQL TagLib (complex and difficult to maintain 
> ? )
> OutputModules+FlowScript (too unknown ? )
> 
> 
> Out of this list, the ability of ModularDBActions to make multiple 
> row/table modifications into a discreet transaction makes it sound the 
> most attractive.
> 
> As for OutputModules+FlowScript, is that even a reality yet?
> 
> 
> Thanks for any advice.
> 
> regards Jeremy
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message