Code Forums - View Single Post - what happens when the OO model makes things too slow?

sde · 09-30-2004, 06:37 AM

i was trying to be pretty strict with my OO approach to the support app i'm developing.

the problem with that is TOO MANY QUERIES! for example, to show an issue history, you need to build the past 10 or so issues for a specific customer.

for each issue, you then need to build a customer object, which calls the phone and product files, and then build an employee object.

with each query costing me from 500-1200ms, this can really add up. i'm dealing with an ibm as/400 -> db2.

the work around i used is to just code a join query in the jsp page itself. this makes things soooo much faster. i only do this when a list of objects need to be viewed which normally would have to execute multiple queries for each row.

what would you do?

09-30-2004, 06:37 AM	#1 (permalink)
sde Moderator Join Date: May 2002 Location: us.ca Posts: 4,505	what happens when the OO model makes things too slow? i was trying to be pretty strict with my OO approach to the support app i'm developing. the problem with that is TOO MANY QUERIES! for example, to show an issue history, you need to build the past 10 or so issues for a specific customer. for each issue, you then need to build a customer object, which calls the phone and product files, and then build an employee object. with each query costing me from 500-1200ms, this can really add up. i'm dealing with an ibm as/400 -> db2. the work around i used is to just code a join query in the jsp page itself. this makes things soooo much faster. i only do this when a list of objects need to be viewed which normally would have to execute multiple queries for each row. what would you do? __________________ Mike