Interesting approach. Unfortunately, in my case, the result set schema
varies for each call.

I'm currently looking at Firebird 2 as an option, given it supports
subqueries (derived tables). The stored procedure code is unwieldy.

-- Garrett

Kevin Lingofelter wrote:

> Hello,
>
> Is the schema of the returned records static? If so, you can create a
> standard table with this structure and add a sessionid field (use
> GUID or whatever) to "fake" a temp table. Using the sessionid, insert
> the records into the table, run your queries then delete the records.
>
> In my case I have a query which returns fields derived by all sorts
> of means and can be pretty intense on resources. The same results are
> used several times in a single application session so instead of
> running the query each time, I have a stored procedure that
> "prepares" the search results by inserting the records into the temp
> table and returning the session ID.
>
> During the session, I can query those results using the session id,
> and clean things up (delete the records) when the session ends.
>
> This works very well, but in my case the schema doesn't change.
>
> Kevin Lingofelter
>
>
>
>
> ------------------------ Yahoo! Groups Sponsor
> --------------------~--> $4.98 domain names from Yahoo!. Register
> anything. http://us.click.yahoo.com/Q7_YsB/neXJAA/yQLSAA/67folB/TM
>

--------------------------------------------------------------------~->

>
>
> Yahoo! Groups Links
>
>
>