Allen Zhang wrote:
Thanks Milena,
Is that means monetdb does not provide final result cache? The result set is fully materialized and delivered to the interface API. Re-use of that particular result set is the responsibility to the client software.
We have sql client will query same query to the database multiple times, imaging each query took 2 minutes to run, that’s will be really painful when the client ask 10 times, since our database is readonly, so a real result cache will really help us.
I would consider it an application design error if a client application issues the same request over and over again. For this, materialized views have been invented and even temporary tables are often used to cope keep expensive results around. Alternatively, database triggers are used to react to changes in the underlying tables. MonetDB has a query cache, which means it will analyse a query once and will reuse the plan whenever possible. And, indeed, the development code contains a recycler, which avoid duplicate work from different users. Provided, it is beneficial to do so. regards, Martin
Regards Allen
------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------
_______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users