Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <3FA2757B.9030304@vafer.org>
Date: Fri, 31 Oct 2003 15:45:15 +0100
From: Torsten Curdt <tcurdt@vafer.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.5) Gecko/20030925
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: ESQL question
References: <20031030110414.GB15819@wlkp.org>
In-Reply-To: <20031030110414.GB15819@wlkp.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

 > Now I see that a simple query without parameters is also prepared
> which makes the execution a lot slower under Pervasive 2000i (I have never
> seen more crappy database).

IIRC this came up before....

> Is it an intentional change ?

Well, yes, kinda....

Ok.. here it goes: when I was doing some work
on esql I found the esql statement handling
to be very ugly.

After some googling it seemed that it's a
consensus that usually (of course depends
on the driver implementation) the prepared
statements are meant to be a faster choice.

Since the code got nicer I changed it that
way ...not exspecting to see such a speed
difference as you might see now (how much
is it?)

So... it seems this is another option per
database. If you could come up with a
nice patch - no problem.


It might not help you in short run...

...but I was already talking to Christian
about this: maybe we should step back
and reanalize the cocoon database
connectivity in general again.

I'd really love to merge esql and the
sql transformer sharing the same syntax
...and more or less the same code. AFA
this is possible...

Maybe it's time to put up a wiki page
where we can collect some RT on a new
sql connectivity.

I am sure we could easily create some
stylesheets for migration to the (maybe?)
new sytax. So this can be pretty painless
for users.

What do you think?
--
Torsten