Clever! That definitely makes this low priority in my mind. I've updated
the bug accordingly.
Cheers,
Percy
On Fri, Nov 2, 2012 at 11:37 AM, Fabian Groffen
On 02-11-2012 11:18:24 -0500, Percy Wegmann wrote:
Thanks, it's filed:
Thanks.
I documented the workaround, which is to not use bind parameters for limit and offset. The major impact here is that it prevents effective caching of the compiled query, since each combo of limit/offset ends up looking like a different query.
Not sure about that. The SQL compiler already factors out constants for queries before it caches them, e.g. select x from t where a > 10 uses the same plan as select x from t where a > 3.
Fabian
_______________________________________________ users-list mailing list users-list@monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list
-- Percy Wegmann +1 512 637 8500 ext 148 _______________________________________________ users-list mailing list users-list@monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list