Re: ESQL / SAP DB troubles : The database detection method has changed

[Geoff Howard <co...@leverageweb.com>]

Torsten? ;)

Geoff

At 07:12 AM 6/6/2003, you wrote:
>Hi,
>
>I m trying to move all my application to Cocoon 2.1-M2 and i'm getting an 
>error when trying to connect to my database, which is SAPDB.
>
>My pool in cocoon.xconf:
>
><jdbc name="Pool-SAPdb">
>        <pool-controller min="10" max="50"/>
>        <dburl>jdbc:sapdb://10.0.0.90/xxx</dburl>
>        <user>xxx</user>
>        <password>xxx</password>
></jdbc>
>
>The error I got:
>
>ERROR   (2003-06-06) 13:07.21:623   [sitemap.generator.serverpages] 
>(/cocoon/isis/do-login) Thread-30/AbstractEsqlConnection: The database 
>detection method has changed.
>If your database is not being recognized (anymore) you can either fix it 
>in the Cocoon2EsqlConnection class,  file it to bugzilla, report it to 
>cocoon-dev or to me (tcurdt.at.apache.org) directly.
>Only be sure to include the database string "sap db" in your post.
>ERROR   (2003-06-06) 13:07.21:623   [sitemap.generator.serverpages] 
>(/cocoon/isis/do-login) Thread-30/auth_user_esql:
>java.sql.SQLException: The database detection method has changed.
>If your database is not being recognized (anymore) you can either fix it 
>in the Cocoon2EsqlConnection class,  file it to bugzilla, report it to 
>cocoon-dev or to me (tcurdt.at.apache.org) directly.
>Only be sure to include the database string "sap db" in your post.
>    at 
> org.apache.cocoon.components.language.markup.xsp.AbstractEsqlConnection.createQuery(AbstractEsqlConnection.java:197)
>    at 
> org.apache.cocoon.www.isis.system.authentication.auth_user_esql.generate(org.apache.cocoon.www.isis.system.authentication.auth_user_esql:364)
>    at 
> org.apache.cocoon.generation.ServerPagesGenerator.generate(ServerPagesGenerator.java:260)
>
>
>Thanks in advance for any hints!
>
>Johann
>
>
>
>
>

Re: ESQL / SAP DB troubles : The database detection method has changed

[Torsten Curdt <tc...@apache.org>]

Geoff Howard wrote:
> Torsten? ;)

I'll take care of this :)

As interim solution you can add

<esql:use-limit-clause>jdbc</esql:use-limit-clause>

cheers
--
Torsten