This doesn't solve the problem. The database must work regardless of whether it
is used within my own app or any other database viewer that might not have the
extension functions available. In the first case, medians, standard deviations,
etc. are included in the view, in the second case the values should be just
NULL.
----- Original Message -----
From: Simon Slavin <slav...@bigfraud.org>
To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org>
Sent: Thursday, May 23, 2019, 12:34:39
Subject: [sqlite] SQL Features That SQLite Does Not Implement
On 23 May 2019, at 7:57am, Thomas Kurz <sqlite.2...@t-net.ruhr> wrote:
> CREATE VIEW foo AS SELECT {if has stddev then stddev(...) else null} FROM ...
'if' in SQL language is CASE.
Near the beginning of your code, try to execute a function that contains
stddev(). Make a note of whether it compiles without errors or not. If it
compiles, then the function is available. Store this boolean somewhere and use
it later on in your code.
What you propose doing: creating a library call which works differently
depending on whether stddev() is available just leads to infinite regress. If
you create such a library call then you'll want to create another library to
tell whether /your/ library call is available.
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
