Hola a Todos:
Got some time to do it ..
This patch adds a Sitemap.xmap component config for SQLtransformer ..
called <old-driver/> ( bad name change it as you like ) setting this
element to true makes SQLtranformer to use the old fashioned
conn.prepareStatement(query); instead the of the JDBC2 ones..
In addition when <old-driver/> is true the rowcount is not calculated
and uses a -1 value instead the number of rows.. This something hard but
was the only solution i found to make SQLtransformer accept the nr-rows
parameter without producing and NonImplemented Exception..
With this 3 changes SQLtransformer will work fine with the interbase
JDBC 1.6 drivers..
Some more comment on excalibur pool and Interbase ..
It seems that the beacon SQL command that excalibur uses to test
connections is failing in interbase because of the ";" included.. but
found some workaround for that problem .. was to use the oradb="true"
attribute when creating the pool in cocoon.xconf and then create a
"DUAL" table in Interbase with 1 row ( to simulate the DUAL oracle table
).. with this 2 measures the excalibur pool works well with interbase..
perhaps this need some clarification or is meat for the faq of Avalon.
Thanks..
Saludos ,
Ignacio J. Ortega
SQLTransformer.java.diff
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
