While it does not provide an example for attached databases, this statement
from documentation seems to apply:
"The PRAGMA argument and schema, if any, are passed as arguments to the
table-valued function."
Maybe you should be doing something similar to
Select pragma_user_version('main'),
The mission statement of the upsert is to fulfil the assertion that a row
exists and the desired change has been recorded therein, while hiding the
details (new row inserted or old row updated) from the caller. Why do you think
you need this information? As already suggested, use a transaction
On Sun, 24 Feb 2019 at 01:55, Tim Streater wrote:
> (sorry for the duplicate - vibrating finger).
>
> I have a hosted web site using the SQLite functions from PHP. The page
> where PHP is used was failing, and on investigation this is because an
> SQLite function called from within PHP is now
No idea how you would call it from PHP, but the sqlite3_system_errno function
may also be of use for determining the underlying cause of the SQLITE_IOERR
error code. https://www.sqlite.org/c3ref/system_errno.html
--
Sent from: http://sqlite.1065341.n5.nabble.com/
2019-02-23 10:03 GMT+01:00, Rocky Ji:
> I went from
>
> https://sqlite.org/lang_createtable.html
>
> to
>
> https://sqlite.org/syntax/table-constraint.html
>
> to
>
> https://sqlite.org/syntax/expr.html
>
> and figured expr of `check` in table constraint may contain a nested select
> after `not
5 matches
Mail list logo
