cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew C. Oliver" <>
Subject [DOCUMENTATION ISSUE] Re: [PROPOSAL] Remove SQLTransformer in 2.1
Date Fri, 12 Jul 2002 12:04:26 GMT
oh and can we remove the "its deprecated" notation from the documentation.

Time permitting, I'll attempt to resolve why it is so slow by comparison.


Carsten Ziegeler wrote:

>Andrew C. Oliver wrote:
>>Hi All,
>>Backward compatibility among minor revisions is generally a smart and 
>>good thing to do.  However, there does
>>become a point where it grows six legs and starts biting you.
>>The ESQL generator AFAIK supports everything one could need to do via 
>>the SQLTransformer and there does not seem
>>to be a reason to continue to support both technologies.
>>IMHO, while the code quality of the ESQL stylesheet is relatively low, 
>>the quality of the SQLTransformer is lower probably due to code rot and 
>>negative evolutionary pressures.
>>I would suppose the SQLTransformer being largely a Cocoon 1.x construct 
>>is reasonable slow and my own unscientific benchmarking seems to confirm 
>>I'd like to propose we remove the SQLTransformer from Cocoon 2.1 and 
>>newer releases, remove all SQLTransformer based samples (or provide esql 
>The SQLTransformer provides a very good alternative to ESQL, it is in
>some use cases more flexible as it is a transformer and not a generator.
>And you don't need XSP to use it.
>The SQLTransformer in its current state is not a 1.x construct, it has
>been redesigned several times and works afaik absolutely perfect. It
>is used in production environments without any problems.
>To unsubscribe, e-mail:
>For additional commands, email:

To unsubscribe, e-mail:
For additional commands, email:

View raw message