daniel.zvinca at logbis.com
Mon Oct 7 16:52:31 CEST 2019
I wasn't sure if this question should be posted here or on regular user
list, considering the way statements are generated and possible connections
with internal functionality.
I understand the explanations. I should have checked the explain feature
myself. I think that I expected the optimizer to notice a constant
expression and evaluate it before choosing which real columnar operation
needs to be performed (obviously only one). Instead all members are
evaluated, the whole explain statement is self-explanatory, indeed. (a
delayed bat evaluation mechanism would have helped, I guess, for this case)
I use capi intensively, but for string columns the capi memory management
can be a serious limitation for large sets.
Anyway, your answer is very helpful for me, it makes me consider adjusting
my approach from a straight translation into one SQL statement into using
an intermediary language that would build the optimal statement instead of
stretching the SQL to get what I need.
On Mon, Oct 7, 2019 at 4:44 PM Sjoerd Mullender <sjoerd at monetdb.org> wrote:
> On 07/10/2019 14.33, Roberto Cornacchia wrote:
> > Hi Daniel,
> > In this case, you would get better performance by implementing a BAT
> > function (not a function that works on a single value, but on a column
> > of values).
> > You would write that in C using the GDK api
> > (
> > and evaluate the condition i the loop, per value.
> > However, this requires you to recompile MonetDB to include your new
> > function.
> Recompilation of MonetDB should not be necessary. See .
>  https://www.monetdb.org/hg/MonetDB-extend/
> Sjoerd Mullender
> developers-list mailing list
> developers-list at monetdb.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the developers-list