You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by bu...@apache.org on 2003/02/03 17:11:11 UTC

DO NOT REPLY [Bug 16718] New: - [PATCH] Using only one connection in SQLTransformer

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16718>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16718

[PATCH] Using only one connection in SQLTransformer

           Summary: [PATCH] Using only one connection in SQLTransformer
           Product: Cocoon 2
           Version: 2.0.4
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: sitemap components
        AssignedTo: cocoon-dev@xml.apache.org
        ReportedBy: danielf@nada.kth.se


In the current implementation of the SQLTransformer, a new db connection is 
created for each <execute-query/> element. This makes it impossible to use 
transactions, temporary tables etc in db:s without stored procedures, e.g. 
MySQL. It is also a waste of cpu cycles. See the thread: 
http://marc.theaimsgroup.com/?t=103978793000002&r=1&w=2 for more details. The 
current patch uses only one connection for each use of the SQLTransformer. 
There is still one connection for each sub query, but there is not much to do 
about that.

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