PFC <[EMAIL PROTECTED]> writes:
> Feature proposal :
> A way to store query results in a named buffer and reuse them in the
> next
> queries.
Why not just fix the speed issues you're complaining about with temp
tables? I see no reason to invent a new concept.
(Now, "just fix" mig
Hi,
On Tue, 9 May 2006, PFC wrote:
You might consider just selecting your primary key or a set of
primary keys to involved relations in your search query. If you
currently use "select *" this can make your result set very large.
Copying all the result set to the temp. costs you additional I
Hi,
On Tue, 9 May 2006, PFC wrote:
Back to the point : I can't use the temp table method, because temp
tables are too slow.
Creating a temp table, filling it, analyzing it and then dropping it
takes about 100 ms. The search query, on average, takes 10 ms.
just some thoughts:
You might con
You might consider just selecting your primary key or a set of
primary keys to involved relations in your search query. If you
currently use "select *" this can make your result set very large.
Copying all the result set to the temp. costs you additional IO
that you propably dont need.
It i
