On 04/06/2011 09:13 PM, Sándor Halász wrote:
I have a temporary table which is a smaller table generated from a rather big
one. The full table is too big to make real gimmicks on it, so I do need the
temp table. Later I do several queries on the temp table.
So my initial setup and needs are:
- temporary table to work from
- result sets derived from parametric queries
- mysql views cannot work from temporary tables so I have to drop a
view+select/where approach.
- functions cannot return result sets
- procedures can do everything but I found no way to handle the result set
within mysql (officially not supported)
Any ideas how to solve this?
<<<<<<<<
Why not fake the temporariness, by DROPping the table as needful?
I 'DROP'ed that approach for a couple of reasons:
- While trying to minimize the load on the big table there is a real
chance of concurrent jobs. Overall I find two temp table generation
(loads) better than dropping each other's tables or locking other jobs.
You also have to keep track of the fake-temp table's age.
- A regular update of the fake-temp table would solve the above, but
would produce too much load at the expected freshness.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
