Re: strange database problem
That looks bad, indeed. I will have a look at it but it will take some time to reproduce these values (gimme a week or so). I take your word for it that you haven't changed anything else around it like move the DBMS to another machine, upgrade your network, CPU, RAM, JDK, JDBC driver or anything else. I've collected these timings today substituting only cocoon directories However, I will not be able to test against your setup and use a different DBMS / OS / JDK / Servlet-Container. To eliminate my fault somewhere please download file from http://ouzo.niebiosa.com/cocoon.rar (rar 3.0 packed - ca. 18 MB ) or http://ouzo.niebiosa.com/cocoon.tar.gz - ca. 27 MB It contains both cocoon versions (apidocs were stripped because of size but I left the rest). I can also send you the database installation file but you'll have to run in on Win32( or someone else who is willing to try to reproduce my results) It would help to have some more information on the table, like number and type of columns, number of rows. at the location http://ouzo.niebiosa.com/table.txt you will find as much table information as I could get the records I'm working on are at http://ouzo.niebiosa.com/records.txt If you care to do some experiments yourself, the ESQL stuff is fairly self-contained and does not depend on other changes in Cocoon. Thus it's only o.a.c.c.l.m.xsp/Esql*.java and o.a.c.c.l.m.xsp.java/esql.xsl The resulting java code produced from your XSP should be fairly similar with both versions, actually. The main difference should be the introduction of various switch statements to select different results. Those are outside the retrieval loop and so should not account for a big slow-down. The other major difference should be, that the current version does not check for another result set while the older version did (in a not JDBC compliant way - that was changed to be compliant and later disabled). Other things happend in the grouping / CallableStatement support which should not be used in your case. What exactly should I do ? ouzo -- __ | / \ |Leszek Gawron// \\ \_\\ //_/ [EMAIL PROTECTED] _\\()//_ .'/()\'. Phone: +48(600)341118 / // \\ \ \\ // recursive: adj; see recursive | \__/ | - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange database problem
On 04.Jul.2002 -- 08:38 AM, Leszek Gawron wrote: That looks bad, indeed. I will have a look at it but it will take some time to reproduce these values (gimme a week or so). I take your word for it that you haven't changed anything else around it like move the DBMS to another machine, upgrade your network, CPU, RAM, JDK, JDBC driver or anything else. I've collected these timings today substituting only cocoon directories Great! OK, I've downloaded the indicated files. If you care to do some experiments yourself, the ESQL stuff is fairly self-contained and does not depend on other changes in Cocoon. Thus it's only o.a.c.c.l.m.xsp/Esql*.java and o.a.c.c.l.m.xsp.java/esql.xsl The resulting java code produced from your XSP should be fairly similar with both versions, actually. The main difference should be the introduction of various switch statements to select different results. Those are outside the retrieval loop and so should not account for a big slow-down. The other major difference should be, that the current version does not check for another result set while the older version did (in a not JDBC compliant way - that was changed to be compliant and later disabled). Other things happend in the grouping / CallableStatement support which should not be used in your case. What exactly should I do ? Well, if you want to spare me the experimenting you could take the ESQL components from one version and replace the other versions, rebuild and retry. If this setup shows the same timings as before (e.g. improve with old ESQL in new C2 or deteriorate with new ESQL in old C2), then it would indicate that it's indeed an ESQL problem. Otherwise something else in C2 is responsible for the performance loss. If it's no ESQL problem, timing differences for other XSPs would be helpful. If they don't differ, it's likely that it's the Avalon Excalibur version that accounts for it. Unfortunately, C2 and Avalon are tightly coupled that it might be difficult to switch versions. Chris. -- C h r i s t i a n H a u l [EMAIL PROTECTED] fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08 - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange database problem
Well, if you want to spare me the experimenting you could take the ESQL components from one version and replace the other versions, rebuild and retry. If this setup shows the same timings as before The problem is I do not have the cocoon sources for older version. If you are able to identify the version and tell me where I can download it from (I think dev snapshots are not archved, are they?) ouzo -- __ | / \ |Leszek Gawron// \\ \_\\ //_/ [EMAIL PROTECTED] _\\()//_ .'/()\'. Phone: +48(600)341118 / // \\ \ \\ // recursive: adj; see recursive | \__/ | - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange database problem
On 04.Jul.2002 -- 05:59 PM, Leszek Gawron wrote: Well, if you want to spare me the experimenting you could take the ESQL components from one version and replace the other versions, rebuild and retry. If this setup shows the same timings as before The problem is I do not have the cocoon sources for older version. If you are able to identify the version and tell me where I can download it from (I think dev snapshots are not archved, are they?) Don't think so. But CVS let's you retrieve any version: (have a current cvs checkout, move to that directory. Description how to obtain such a version can be found on http://xml.apache.org/cvs.html) cvs update -d -P -D 2002-04-20 . I belive checkout takes the -D option as well. In case you cannot use CVS, there's a web interface on http://cvs.apache.org/viewcvs.cgi/xml-cocoon2/ that lets you retrieve older versions as well. It's only 4 or 5 files. Chris. -- C h r i s t i a n H a u l [EMAIL PROTECTED] fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08 - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange database problem
Since multiple important DBMSs have problems with checking for multiple result sets, it has been disabled by default for the current CVS version. It can be re-enabled by using esql:allow-multiple-resultsyes/esql:allow-multiple-results Option to esql:connection/. Please try again with a snap shot newer than 2002-06-28 It works quite fine with only one small but: I was using cocoon version from april ( 2002.04.20 i think ). The response times (after compiling the xsp page) where somewhere about 80-190 ms. Now it's 200-400 ms and sometimes more. What may cause such great difference in response times? The xsp file is really simple: it does select * from tablename only and outputs all columns. The recordset retrieved contains 23 records (about 20 columns each). ouzo -- __ | / \ |Leszek Gawron// \\ \_\\ //_/ [EMAIL PROTECTED] _\\()//_ .'/()\'. Phone: +48(600)341118 / // \\ \ \\ // recursive: adj; see recursive | \__/ | - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange database problem
On Tue, Jul 02, 2002 at 12:09:35PM +0200, Christian Haul wrote: On 02.Jul.2002 -- 11:55 AM, Leszek Gawron wrote: Since multiple important DBMSs have problems with checking for multiple result sets, it has been disabled by default for the current CVS version. It can be re-enabled by using esql:allow-multiple-resultsyes/esql:allow-multiple-results Option to esql:connection/. Please try again with a snap shot newer than 2002-06-28 It works quite fine with only one small but: I was using cocoon version from april ( 2002.04.20 i think ). The response times (after compiling the xsp page) where somewhere about 80-190 ms. Now it's 200-400 ms and sometimes more. What may cause such great difference in response times? The xsp file is really simple: it does select * from tablename only and outputs all columns. The recordset retrieved contains 23 records (about 20 columns each). Mmmh, nothing that comes to mind should have a significant effect on performance. Someone suggested using a different driver, so, did you measure the different response times with the same driver? Does performance degenerate over time? It is the very same jadozoom driver. I cannot tell if the performance degenerates but I think not. The difference is significant though. ouzo -- __ | / \ |Leszek Gawron// \\ \_\\ //_/ [EMAIL PROTECTED] _\\()//_ .'/()\'. Phone: +48(600)341118 / // \\ \ \\ // recursive: adj; see recursive | \__/ | - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange database problem
On 02.Jul.2002 -- 03:09 PM, Leszek Gawron wrote: On Tue, Jul 02, 2002 at 12:09:35PM +0200, Christian Haul wrote: On 02.Jul.2002 -- 11:55 AM, Leszek Gawron wrote: Since multiple important DBMSs have problems with checking for multiple result sets, it has been disabled by default for the current CVS version. It can be re-enabled by using esql:allow-multiple-resultsyes/esql:allow-multiple-results Option to esql:connection/. Please try again with a snap shot newer than 2002-06-28 It works quite fine with only one small but: I was using cocoon version from april ( 2002.04.20 i think ). The response times (after compiling the xsp page) where somewhere about 80-190 ms. Now it's 200-400 ms and sometimes more. What may cause such great difference in response times? The xsp file is really simple: it does select * from tablename only and outputs all columns. The recordset retrieved contains 23 records (about 20 columns each). Mmmh, nothing that comes to mind should have a significant effect on performance. Someone suggested using a different driver, so, did you measure the different response times with the same driver? Does performance degenerate over time? It is the very same jadozoom driver. I cannot tell if the performance degenerates but I think not. The difference is significant though. Just double checking. You've upgraded from 2.0.2 to 2.1-dev (snapshot), right? Could you try the same with a 2.0.3 CVS version? (Don't know enough about WinCVS www.wincvs.org to give instructions, this is command line cvs usage) cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic login password: anoncvs cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic checkout -r cocoon_2_0_3_branch xml-cocoon2 Build cocoon: cd xml-cocoon2 bash build.sh -Dinclude.webapp.libs=yes webapp WAR is in build/cocoon/ Remember to clear $TOMCAT/work before restarting. TIA. Chris. -- C h r i s t i a n H a u l [EMAIL PROTECTED] fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08 - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange database problem
It is the very same jadozoom driver. I cannot tell if the performance degenerates but I think not. The difference is significant though. ouzo here are some timings taken from cocoon log: version somewhere round 2002.04.20 INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 2.453 seconds. DEBUG HttpProcessor[80][4]/AbstractEnvironment: Resolving 'docs/samples/xsp/esql2.xsp' in context 'file:/C:/Dev/Tomcat/webapps/ROOT/' DEBUG HttpProcessor[80][4]/AbstractEnvironment: Resolving 'docs/samples/xsp/esql2.xsp' in context 'file:/C:/Dev/Tomcat/webapps/ROOT/' INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 270 milliseconds. DEBUG HttpProcessor[80][4]/AbstractEnvironment: Resolving 'docs/samples/xsp/esql2.xsp' in context 'file:/C:/Dev/Tomcat/webapps/ROOT/' DEBUG HttpProcessor[80][4]/AbstractEnvironment: Resolving 'docs/samples/xsp/esql2.xsp' in context 'file:/C:/Dev/Tomcat/webapps/ROOT/' INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 140 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 110 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 200 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 211 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 110 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 190 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 120 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 111 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 200 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 110 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 230 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 100 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 220 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 110 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 110 milliseconds. version 2002.07.01 INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 5.378 seconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 460 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 250 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 270 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 280 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 300 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 231 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 270 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 201 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 270 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 771 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 321 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 300 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 300 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 210 milliseconds. INFO HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev in 300 milliseconds. there was no performance tuning, no other pages are created just standard cocoon installation + one xsp file (and jdbc driver of course) ouzo -- __ | / \ |Leszek Gawron// \\ \_\\ //_/ [EMAIL PROTECTED] _\\()//_ .'/()\'. Phone: +48(600)341118 / // \\ \ \\ // recursive: adj; see recursive | \__/ | - Please check that your question has
Re: strange database problem
Just double checking. You've upgraded from 2.0.2 to 2.1-dev (snapshot), right? Could you try the same with a 2.0.3 CVS version? Both cocoon versions are 2.1-dev (downloaded as cvs snapshots) ouzo -- __ | / \ |Leszek Gawron// \\ \_\\ //_/ [EMAIL PROTECTED] _\\()//_ .'/()\'. Phone: +48(600)341118 / // \\ \ \\ // recursive: adj; see recursive | \__/ | - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange database problem
On 30.Jun.2002 -- 01:26 PM, Peter Royal wrote: On Sunday 30 June 2002 01:24 pm, Leszek Gawron wrote: com.inzoom.adojni.ComException: Current provider does not support returning multiple recordsets from a single execution. in ADODB.Recordset code=0 Type=1 First I thought that it's something wrong with msde provider or jdbc driver but getting back to 2002.04.21 dev snapshot makes the error disappear. The esql logicsheet is now using JDBC features that your driver does not support. Since multiple important DBMSs have problems with checking for multiple result sets, it has been disabled by default for the current CVS version. It can be re-enabled by using esql:allow-multiple-resultsyes/esql:allow-multiple-results Option to esql:connection/. Please try again with a snap shot newer than 2002-06-28 Chris. Please follow up summarizing your problem and which suggested solution / information worked for you. Add SUMMARY: to the subject line. This will make FAQ generation and searching the list easier. In addition, it makes helping you more fun. Thank you. -- C h r i s t i a n H a u l [EMAIL PROTECTED] fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08 - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange database problem
On Sunday 30 June 2002 01:24 pm, Leszek Gawron wrote: com.inzoom.adojni.ComException: Current provider does not support returning multiple recordsets from a single execution. in ADODB.Recordset code=0 Type=1 First I thought that it's something wrong with msde provider or jdbc driver but getting back to 2002.04.21 dev snapshot makes the error disappear. The esql logicsheet is now using JDBC features that your driver does not support. You might try the JDBC driver available from microsoft: http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/001/779/msdncompositedoc.xml or http://makeashorterlink.com/?S10911A21 if the above wraps and doesn't work correctly. -pete -- peter royal - [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange database problem
The esql logicsheet is now using JDBC features that your driver does not support. I do not really think that is a problem. See what gets generated: row Twr_TwrId22/Twr_TwrIdTwr_Typ0/Twr_TypTwr_KodNIWELACJA/Twr_KodTwr_NumerKat020/Twr_NumerKatTwr_SWW/Twr_EAN/Twr_NazwaNiwelacja ogrodu, przygotowanie do nasadzeń/Twr_NazwaTwr_GrupaUSŁUGI/Twr_GrupaTwr_URL/Twr_KatId55/Twr_KatIdTwr_KategoriaWykonanie ogrodów/Twr_KategoriaTwr_Opis/Twr_EdycjaNazwy0/Twr_EdycjaNazwyTwr_KopiujOpis1/Twr_KopiujOpisTwr_EdycjaOpisu0/Twr_EdycjaOpisuTwr_JMDZIEŃ/Twr_JMTwr_JMZ/Twr_JMPrzelicznikL1/Twr_JMPrzelicznikLTwr_JMPrzelicznikM1/Twr_JMPrzelicznikMTwr_JMCalkowite0/Twr_JMCalkowiteTwr_TwCNumer2/Twr_TwCNumerTwr_UdostepniajWCenniku0/Twr_UdostepniajWCennikuTwr_KosztUslugi70/Twr_KosztUslugiTwr_KosztUslugiTyp1/Twr_KosztUslugiTypTwr_Stawka22/Twr_StawkaTwr_Flaga2/Twr_FlagaTwr_Zrodlowa0/Twr_ZrodlowaTwr_OpeZalID3/Twr_OpeZalIDTwr_TS_Zal2000-11-15 10:37:37/Twr_TS_ZalTwr_OpeModID1/Twr_OpeModIDTwr_TS_Mod2001-11-23 09:41:17/Twr_TS_ModTwr_KatZakId55/Twr_KatZakIdTwr_KategoriaZakWykonanie ogrodów/Twr_KategoriaZakTwr_StawkaZak22/Twr_StawkaZakTwr_FlagaZak2/Twr_FlagaZakTwr_ZrodlowaZak0/Twr_ZrodlowaZak /row row Twr_TwrId23/Twr_TwrIdTwr_Typ1/Twr_TypTwr_KodGRABKI/Twr_KodTwr_NumerKat021/Twr_NumerKatTwr_SWW/Twr_EAN201000106/Twr_EANTwr_NazwaGrabki do liści/Twr_NazwaTwr_GrupaAKCESORIA/Twr_GrupaTwr_URL/Twr_KatId17/Twr_KatIdTwr_KategoriaSprzedaż akcesoriów ogrodniczych/Twr_KategoriaTwr_Opis/Twr_EdycjaNazwy1/Twr_EdycjaNazwyTwr_KopiujOpis1/Twr_KopiujOpisTwr_EdycjaOpisu1/Twr_EdycjaOpisuTwr_JMSZT/Twr_JMTwr_JMZ/Twr_JMPrzelicznikL1/Twr_JMPrzelicznikLTwr_JMPrzelicznikM1/Twr_JMPrzelicznikMTwr_JMCalkowite0/Twr_JMCalkowiteTwr_TwCNumer2/Twr_TwCNumerTwr_UdostepniajWCenniku0/Twr_UdostepniajWCennikuTwr_KosztUslugi0/Twr_KosztUslugiTwr_KosztUslugiTyp1/Twr_KosztUslugiTypTwr_Stawka7/Twr_StawkaTwr_Flaga2/Twr_FlagaTwr_Zrodlowa0/Twr_ZrodlowaTwr_OpeZalID3/Twr_OpeZalIDTwr_TS_Zal2000-11-15 14:51:36/Twr_html xmlns:error=http://apache.org/cocoon/error/2.0; head META http-equiv=Content-Type content=text/html; charset=UTF-8 titleerror:An error occurred/title style 23 rows get generated and suddenly one of the tags does not get closed: Twr_TS_Zal2000-11-15 14:51:36/Twr_html xmlns:error=http://apache.org/cocoon/error/2.0; ^^ in here if my driver does not support logicsheet functionality howcome do I see some data from db? ouzo -- -- [EMAIL PROTECTED] Leszek GawronICQ# 19681190 Software development SE consulting Mobile +48 (608) 23 74 55 - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange database problem
The esql logicsheet is now using JDBC features that your driver does not support. the older version that works for me is 1.18 the one that does not: 1.28 -- -- [EMAIL PROTECTED] Leszek GawronICQ# 19681190 Software development SE consulting Mobile +48 (608) 23 74 55 - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
