Alan,

Why is it that you insist on this model?

Your application will not scale if you insist on causing an entire dataset
to be scanned on the server just to fetch a single record out of it.

IBO needs to be enhanced as I suggested earlier for this to work in a
totally efficient manner. It is on my list of things to do. Perhaps you
can twist my arm a little if you provide for me a good working model to
operate with when designing this.

You will need at least two stored procedures. One for the whole dataset and
another with additional columns parameters for keylinks columns that will
return an individual record.

It may also be possible to use a single procedure as well, you would just
have the keylinks columns as parameters and when you want your whole dataset
put NULL in them and take that to mean a whole dataset request, however, if
there are values in those parameters then take it as a single record request
and then inside your stored procedure you can handle each case efficiently.

I hope this helps clarify where the root issues of efficiency, and IBO's
current deficiency in addressing this is at.


Jason Wharton

> -----Original Message-----
> From: Alan McDonald [mailto:alan@...]
> Sent: Monday, November 01, 2004 3:49 PM
> To: IBObjects@yahoogroups.com
> Subject: RE: [IBO] IB_Query/SP/KeyLinks
>
>
>
> >
> > Using a WHERE clause on select procedures is VERY expensive
> to the server.
> > I don't recommend you do this unless it is for very minor
> adjustments.
> >
> > Jason Wharton
>
> as I said - I'm only testing/deveoping at this time (and it's quite
> acceptable anyway)
> Alan