Hi Carsten, unfortunately for you, the database behaviour is that this error is always reported, only stripped away in case of single statements. Also, the database stops processing at the first error, meaning that some of the commands are not executed - and this is more worth to throw the exception than the error itself.
In single statements, this error is ignored actively by the driver, as also here an empty result set or an update count of zero speaks for itself here and is more convenient, and there is no unintentional loss of data in this case. There is not much chance to change this. Regards Alexander Schr�der > -----Original Message----- > From: Carsten Tolkmit [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 18, 2002 4:41 PM > To: Maillingliste SAPDB > Subject: Possible JDBC-Bug? > > > Hi, > > I use sapdb-jdbc-bin-7.3.00.29a.jar as downloaded from ftp.sap.com. > > I am programming an applications using the hibernate persistence > framework (hibernate.sourceforge.net). It is using a lot of batch > updates. > > At a certain point I get: > > --- schnipp --- > > com.sap.dbtech.jdbc.exceptions.BatchUpdateExceptionSapDB: SAP DBTech > SQL: > [100] Row not found > at > com.sap.dbtech.jdbc.CallableStatementSapDB.executeBatch(Callab > leStatementSap > DB.java:467) > at > cirrus.hibernate.impl.SessionImpl.executeBatch(SessionImpl.java:2406) > at > cirrus.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:1669) > at > cirrus.hibernate.impl.SessionImpl.execute(SessionImpl.java:1648) > at > cirrus.hibernate.impl.SessionImpl.flush(SessionImpl.java:1591) > at > cirrus.hibernate.transaction.JDBCTransaction.commit(JDBCTransa > ction.java:51) > at > _0002factions_0002ejspactions_jsp_48._jspService(_0002factions > _0002ejspactio > ns_jsp_48.java:302) > at > org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119) > at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > org.apache.jasper.servlet.JspServlet$JspServletWrapper.service > (JspServlet.ja > va:177) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet > .java:318) > at > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:391) > at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper > .java:404) > at org.apache.tomcat.core.Handler.service(Handler.java:286) > at > org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) > at > org.apache.tomcat.core.ContextManager.internalService(ContextM > anager.java:79 > 7) > at > org.apache.tomcat.core.ContextManager.service(ContextManager.java:743) > at > org.apache.tomcat.service.http.HttpConnectionHandler.processCo > nnection(HttpC > onnectionHandler.java:210) > at > org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoin > t.java:416) > at > org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPo > ol.java:498) > at java.lang.Thread.run(Thread.java:536) > > --- schnapp --- > > Well, I know that one of the updates for sure will update NO rows. But > that should not raise an exception, should it? > > The queries look ok to me, otherwise. > > Best regards, > Carsten > -- > Carsten Tolkmit <[EMAIL PROTECTED]> > TNG - THE NET GENERATION GmbH > > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general > _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
