Hi, We have the same problem. This is because OJB does not (yet?) implement paging based on RDBMS native paging/limiting syntax. A query, hitting the complete resultset is executed and cursors are used to fetch the requested page. Large resultsets, will take a lot of time.
We have been experiencing more and more problems over the last few years with this. I am wating for the OJB 1.1 release (For over 2 years now!) and hoping that it will implemented this feature. Right now, I have to expose the datamodel within my application code, bypassing our domain model and OJB as OR mapper, and that really hurts. Greetings, Roger Janssen iBanx -----Original Message----- From: Ferrer, Eric [mailto:[EMAIL PROTECTED] Sent: vrijdag 2 februari 2007 3:54 To: OJB Users List Subject: RE: Performance Issue on lookup on a table Just to add it appears to work when passing a straight SQL query versus using the persistable method. -Eric -----Original Message----- From: Ferrer, Eric [mailto:[EMAIL PROTECTED] Sent: Thursday, February 01, 2007 4:57 PM To: OJB Users List Subject: RE: Performance Issue on lookup on a table Sorry Accidently hit send. What I was saying the query generate looks like this SELECT TOP 1 A0.SERIAL_NUMBER,A0.AD_ID,A0.LIC_NUM,A0.RECEIVED_DTIME,A0.LIC_ST,A0.LIC_ TYPE FROM MY_LIC_TLB A0 WHERE ((A0.LIC_NUM = '1236713' ) AND A0.LIC_ST = 'DD' ) AND A0.LIC_TYPE = 'NORMAL' When I run it in the sql management tool it comes back in less than 20 seconds, however via ojb it varies between 5 and 7 minutes. The table has 3 gigs of data. Any ideas what can be the difference? We do lots of similar calls and this is the first one we ever experienced this with. Thanks -Eric -----Original Message----- From: Ferrer, Eric [mailto:[EMAIL PROTECTED] Sent: Thursday, February 01, 2007 4:52 PM To: OJB Users List Subject: Performance Issue on lookup on a table I am experience an issue with an OJB query using a persistable object. Basically its taking 7 minutes to return on the call getObjectByQuery. When I run the query --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ************************************************************************* The information contained in this communication is confidential and is intended solely for the use of the individual or entity to whom it is addressed.You should not copy, disclose or distribute this communication without the authority of iBanx bv. iBanx bv is neither liable for the proper and complete transmission of the information has been maintained nor that the communication is free of viruses, interceptions or interference. If you are not the intended recipient of this communication please return the communication to the sender and delete and destroy all copies. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
