Jay Sprenkle schrieb:
On 9/6/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:The only way I know to provide some approximation of random access cursors for queries like the above is to store the complete result of the query in a temporary table. You can always do so by prepending:Did anyone suggest doing that to them? It seems a simple matter to select the unique keys from the set you want and cache them.
What do you mean? That's the same problem like above. ;-)There is no problem to cache the querys and get information from it. The problem is that it will take A LOT of ressources to get the information. After EVERY call for information you must close the query to the resultset (and OOo will call many functions). OOo has more than one window and maybe a user wants to create/drop a table while he is watching another table. So you need to close your temp table-query or he won't be able to create/drop his tables.
There is no problem to have the resultset in a temp table.I think we will use a cache for a cache now to avoid massive SELECT-usage... that isn't pretty but it will work.
Temp Tables are in separate files... so I hope it will be possible someday to drop/create tables in the main-database while one cursor is pending on the temp-table. ;-)
Regards, André Klitzing
signature.asc
Description: OpenPGP digital signature
