Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 45551 invoked from network); 18 Oct 2000 09:42:13 -0000 Received: from smtp3.mail.yahoo.com (HELO smtp1b.mail.yahoo.com) (128.11.68.135) by locus.apache.org with SMTP; 18 Oct 2000 09:42:13 -0000 Received: from miwis.sisu.se (HELO miwis) (192.71.57.141) by smtp.mail.vip.suc.yahoo.com with SMTP; 18 Oct 2000 09:42:13 -0000 X-Apparently-From: Message-ID: <004001c038e7$ca21fdc0$8d0aa8c0@framkom.se> From: "beichuang" To: , , References: <003e01c0384b$6f607930$8d0aa8c0@framkom.se> Subject: Correct a mistake comment with JDBC/ODBC and another further question!! Date: Wed, 18 Oct 2000 11:42:51 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_003D_01C038F8.8BC03BD0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------=_NextPart_000_003D_01C038F8.8BC03BD0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable hello, all I verified the Cocoon1.8 & JDBC/ODBC bridge class and Turbine engine = again this morning, and here is my final result: The adaptor name DBOdbc is no use, as to why I succeed yesterday, maybe = I didn't update two cocoon.properties file both in webapp directory = below tomcat director "tomcat/webapp/cocoon.properties" and my new = example directory "webapp/mysamples/cocoon.properties". So it means you have to change a line like this to fool Turbine to load = JDBC/ODBC java class: #a trick to replace informix driver with jdbc2odbc driver # = processor.xsp.pool.database.adaptor.DBInformix=3Dcom.informix.jdbc.IfxDri= ver processor.xsp.pool.database.adaptor.DBInformix=3Dsun.jdbc.odbc.JdbcOdbcDr= iver However, I find that if I just define driver in xsp file instead of = using tag MyDBOdbc: sun.jdbc.odbc.JdbcOdbcDriver jdbc:odbc:MyDBTest test test SELECT * FROM tabell1

no results were found

then, I won't bother to setup turbine engine in cocoon.properties file. So I wonder what the difference is between using turbine engine or not? = any outstanding advantages with turbine engine? Addtionally, Now I wonder whether I can set a page-division to my = request? Normally, if a sql request get too many records, I would rather = get some fixed amount records each time, for example, just return 20 = records once, but still I have to continue the query, is it easy to do = with cocoon? I know one can get the whole records once, and just display = some, but maybe it is not the best solution, anymore has comments about = this? I think it very common, and maybe can be put into consideration = earlier. Best regards! ------=_NextPart_000_003D_01C038F8.8BC03BD0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

hello, all

I verified the Cocoon1.8 & = JDBC/ODBC bridge=20 class and Turbine engine again this morning, and here is my final=20 result:

The adaptor name DBOdbc is no use, as = to why I=20 succeed yesterday, maybe I didn't update two cocoon.properties file both = in=20 webapp directory below tomcat director=20 "tomcat/webapp/cocoon.properties" and my new example=20 directory "webapp/mysamples/cocoon.properties".

So it means you have to change a line = like this to=20 fool Turbine to load JDBC/ODBC java class:

#a trick to replace informix driver = with jdbc2odbc=20 driver
# =20 processor.xsp.pool.database.adaptor.DBInformix=3Dcom.informix.jdbc.IfxDri= ver
processor.xsp.pool.database.adaptor.DBInformix=3Dsun.jdbc.odbc.Jdb= cOdbcDriver

However, I find that if I just define = driver in xsp=20 file instead of using tag=20 <esql:use-connection>MyDBOdbc</esql:use-connection>:

<esql:execute-query>
<esql:driver>sun.jdbc.odbc.J= dbcOdbcDriver</esql:driver>
<esql:dburl>jdbc:odbc:MyDBTest= </esql:dburl>
<esql:username>test</esql:username><esql:password>test</esql:password>
   &nb= sp;    =20 <esql:query>
        &nb= sp;      =20 SELECT * FROM = tabell1
         =20 </esql:query>
        &n= bsp;    =20 <esql:results>
        &= nbsp;      =20 <ID><esql:get-string=20 column=3D"ID"/></ID>
      &nbs= p;        =20 <FN><esql:get-string=20 column=3D"First_Name"/></FN>
     &n= bsp;       =20 </esql:results>
        =      =20 <esql:no-results>
       &nbs= p;       =20 <error>no results were=20 found</error>
        &n= bsp;    =20 </esql:no-results>
</esql:execute-query>

then, I won't bother to setup turbine engine in = cocoon.properties=20 file.

So I wonder what the difference is between using turbine engine or = not? any=20 outstanding advantages with turbine engine?

Addtionally, Now I wonder whether I can set a = page-division to my request? Normally, if a sql request get too many = records, I=20 would rather get some fixed amount records each time, for example, just = return=20 20 records once, but still I have to continue the query, is it easy to = do with=20 cocoon? I know one can get the whole records once, and just display = some,=20 but maybe it is not the best solution, anymore has comments about this? = I think=20 it very common, and maybe can be put into consideration = earlier.

Best regards!

------=_NextPart_000_003D_01C038F8.8BC03BD0-- _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com