Re: [sqlite] Clarification of overloading built-in funcs

Hi! Correct, but Richard's answer clarified it, at least enough for my use case. Maybe "at some point" it might be worth the effort to distinguish them in the docs, but if it hasn't been an issue so far then i see to compelling need. (sent from a mobile device - please excuse brevity, typos, and

Re: [sqlite] Clarification of overloading built-in funcs

Richard, I think the confusion is between OVERRIDE and OVERLOAD, and in what cases defining a function is an complete override of the function (and all its pre-existing overloaded implementations), and in what cases it is merely an OVERLOAD of the function name. And of course whether it is

Re: [sqlite] Clarification of overloading built-in funcs

If you call sqlite3_create_function_v2() with a function name that is the name of a built-in function, then the built-in function goes away and is replaced by your application-defined function. The original built-in function is no longer accessible. *Any* built-in function can be overloaded in

[sqlite] Clarification of overloading built-in funcs

Hi, all, i'm looking for a clarification on what is certainly a bit of pedantry on my part: http://www.sqlite.org/c3ref/create_function.html specifies that we can overload built-in funcs with UDFs: "Built-in functions may be overloaded by new application-defined functions." Does "overload"