Re: SQLTransformer good, ESQL bad

2002-08-18 Thread Christian Haul
On 18.Aug.2002 -- 07:19 PM, Jan Willem Penterman wrote: > > Could you please try to find if your logs contain something > > like "could not acquire a Connection -- waiting" and set the > > parameter 1 in the > > declaration of the transformer in sitemap.xmap? > > No only the 'no suitable drive

RE: SQLTransformer good, ESQL bad

2002-08-18 Thread Jan Willem Penterman
> Could you please try to find if your logs contain something > like "could not acquire a Connection -- waiting" and set the > parameter 1 in the > declaration of the transformer in sitemap.xmap? No only the 'no suitable driver' error when calling the esql page.. And SQLTransformer works just

Re: SQLTransformer good, ESQL bad

2002-08-18 Thread Christian Haul
On 17.Aug.2002 -- 11:13 PM, Jan Willem Penterman wrote: > I'm sorry to the spam the list like this, but now I've got the feeling > I'm really getting somewhere: > > I've set up cocoon-2.0.3 binary release for j2sdk1.4 and added a pool > for MySQL Connector/J . > > Now I've actually managed to ge

RE: SQLTransformer good, ESQL bad

2002-08-17 Thread Luca Morandini
Jan, well, I use SQLTranformer and not ESQL, for two basic reasons: 1) it does Stored Procedures just fine (and a year before ESQL did) 2) I don't like to be restricted to the generation step when it comes to SQL (as happens using XSP)... though I have to admit I dislike XSP all the way On the

Re: SQLTransformer good, ESQL bad

2002-08-17 Thread Andrew C. Oliver
>From the information provided it is not immediately apparent to me what your problem is. But from crude benchmarking I've done.. ESQL is SIGNIFICANTLY faster than the SQLTransformer.. To experience this, use apbench on the http://localhost:8080/cocoon/samples/poi/statetax.xls and statetax2.xls