The SQLite CLI is a handy tool for explaining query plans and virtual
machine opcodes. Unfortunately it mostly doesn't do me any good because
of user-defined functions in triggers:
sqlite> explain insert into changes default values;
Error: no such function: debug
It would be quite useful
What about loading your UDF in the CLI?
-Ursprüngliche Nachricht-
Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im
Auftrag von no...@null.net
Gesendet: Mittwoch, 29. November 2017 09:58
An: SQLite mailing list
Betreff: [EXTERNAL] [sqlite] Ignore missing UDFs for
On Wed Nov 29, 2017 at 09:21:47AM +, Hick Gunter wrote:
> What about loading your UDF in the CLI?
Do you mean with a .so/.dll? Most of my UDFs are written in Perl, as is
much of the rest of my code, and are not standalone compiled objects.
It would be sufficent if there was a way to write stu
You need to duplicate whatever method you use to load your UDFs in your
application - which in the end boils down to calling sqlite3_create_function()
with appropriate arguments that cause "glue code" to be executed- into the CLI.
Then make that code available as an extension or a new ".perlfunc
E.Pasma wrote
>> What about changing the remaining inner join to left join
>
>> Select BaseTbl.RowID
>> from BaseTbl
>> left join Tbl_2 on Tbl2.Y = BaseTbl.Y
>> where BaseTbl.Col=?
>
>> and see if the SQLiter optimizer now leaves Tbl_2 out from the query
>> plan. It will only do that if it is not
http://www.sqlite.org/compile.html
SQLITE_ENABLE_UNKNOWN_SQL_FUNCTION
When the SQLITE_ENABLE_UNKNOWN_SQL_FUNCTION compile-time option is
activated, SQLite will suppress "unknown function" errors when running an
EXPLAIN or EXPLAIN QUERY PLAN. Instead of throwing an error, SQLite will insert
On Tue, Nov 28, 2017 at 10:07 AM, Dominique Devienne
wrote:
> On Sat, Oct 29, 2016 at 8:09 AM, Dan Kennedy
> wrote:
>
>> On 10/29/2016 12:28 PM, jungle Boogie wrote:
>>
>>> Hi Dr. Hipp,
>>>
>>> Probably a low concern for you at 1:30am your time but I can't connect
>>> to fossil-scm.org or sqlite
*I’m now wondering if you omit the WHERE & ORDER BY and run the following
EXPLAIN QUERY PLAN
SELECT BaseTbl.RowID
FROM BaseTbl
left join Tbl1 on comparison_1
left join Tbl2 on comparison_2
.
.
left join Tbln on comparison_n
then if it returns more than 1 row then this implies there’s a 1
On Tue, Nov 28, 2017 at 9:33 PM, J. King wrote:
> ...*that I never thought to ask*, many of which have been helpful in
> refining my application. ...
>
+1 that.
That is the main advantage of a mailing list over a forum with
filter-bubble or god forbid 'personalization'.
I even miss the keyword s
9 matches
Mail list logo