Re: Query result times in WO and mysql
Re: Query result times in WO and mysql
- Subject: Re: Query result times in WO and mysql
- From: Klaus Berkling <email@hidden>
- Date: Wed, 21 Jan 2004 07:55:03 -0800
On Tuesday, January 20, 2004, at 06:38 PM, Jake MacMullin wrote:
What are you doing with the results of the query? I don't know much
about the performance penalty of simply executing a query from WO -
but most of the time, executing a query in WO results in the creation
of many objects (1 for each row of the table) - There will always be
an overhead involved in creating Java objects - my guess is that this
is the primary cause for your query taking longer - rather than
anything to do with the database/webobjects communication - although I
could be wrong.
That makes sense.
Rather than seeing this as a limitation of WebObjects - it may just
bring design decisions in to focus. Why do you need to retrieve 5500
rows from your database for example? Are you going to display them
all? Why not just fetch the number of rows that your users need at any
one time?
The large number of records is raw data that gets processed by the
client application which is not a web browser. If it were I'd do more
processing on the server side. :-)
Changing the architecture of the client is not a option. It more
likely that the client is eliminated in leu of a web browser front end
- I hope.
kib
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.