Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3D2DEE35.3090402@apache.org>
Date: Thu, 11 Jul 2002 16:44:37 -0400
From: "Andrew C. Oliver" <acoliver@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.0.0) Gecko/20020530
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: [PROPOSAL] Remove SQLTransformer in 2.1
References: <20020711163242.1505.qmail@web20419.mail.yahoo.com>
 <3D2DCEC5.4040905@pandora.be>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

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 
this.

I'd like to propose we remove the SQLTransformer from Cocoon 2.1 and 
newer releases, remove all SQLTransformer based samples (or provide esql 
alternatives).

Thoughts?

-Andy

Tom Klaasen wrote:

> Joshua McCulloch wrote:
>
>> The queries are definitely not taking 130ms outside of
>> cocoon.
>>
>
> Can you put numbers on this? How much does it take to do the same 
> queries in a simple java program? (setup connections, start timer, 
> execute queries, stop timer)
>
> And on another note: does it also takes 130 ms if the SQLTransformer 
> is already executed some times? The first time, you have overhead in 
> creating connections etc, while after some times, the connections are 
> taken from a pool.
>
>>
>> What do you mean by turning off debugging? I've
>> changed the logging status to ERROR, and saw some
>> improvement. What did you turn off, and how did you do
>> so?
>>
>
> That's what I meant: change logging status to ERROR. I'm not sure 
> though if this can still be done on one place, or if there are more 
> places nowadays where you can reduce the logging level (yeah, I know, 
> my in-depth days of Cocoon are some time behind me already. I hope I 
> can get to work on some Cocoon project again, but that won't be in the 
> near future).
>
>> Thanks! :)
>>
>
> np, that's what we're here for ;)
>
> tomK
>
>
>
> ---------------------------------------------------------------------
> Please check that your question  has not already been answered in the
> FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail:     <cocoon-users-unsubscribe@xml.apache.org>
> For additional commands, e-mail:   <cocoon-users-help@xml.apache.org>
>
>


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