> Le 9 mai 2017 à 00:21, Simon Slavin a écrit :
>
> Hardly anyone uses the authentication system, so far fewer people know the
> answers.
As a reminder, I intend to use the authorisation system in order to tell if a
statement has an opportunity to impact on another statement, as a support for
> Le 9 mai 2017 à 00:21, Simon Slavin a écrit :
>
>
> On 8 May 2017, at 10:11pm, petern wrote:
>
>> Who is the author of the Authorizer Action Code source?
>
> Although SQLite is in the public domain, development of it is not typical for
> an open source project. Almost everything you down
> Le 8 mai 2017 à 23:11, petern a écrit :
>
> Gwendal. I understand all that. It's also good that you've confirmed how
> SQLITE_READ is actually queried by the authorizer callback interface. I
> was wondering about that. Reading your earlier post, one might get the
> impression that the SQLI
On 8 May 2017, at 10:11pm, petern wrote:
> Who is the author of the Authorizer Action Code source?
Although SQLite is in the public domain, development of it is not typical for
an open source project. Almost everything you download when you download
SQLite was written by a development team o
Gwendal. I understand all that. It's also good that you've confirmed how
SQLITE_READ is actually queried by the authorizer callback interface. I
was wondering about that. Reading your earlier post, one might get the
impression that the SQLITE_READ authorizer action was not queried by the
engine
On Mon, May 8, 2017 at 8:20 PM, Scott Robison
wrote:
> On Mon, May 8, 2017 at 11:40 AM, Paul van Helden
> wrote:
> > Hi,
> >
> > I use a lot of indexes on fields that typically contain lots of NULLs, so
> > the WHERE NOT NULL partial indexing seems very useful.
> >
> > However when I compare the
On Mon, May 8, 2017 at 11:40 AM, Paul van Helden wrote:
> Hi,
>
> I use a lot of indexes on fields that typically contain lots of NULLs, so
> the WHERE NOT NULL partial indexing seems very useful.
>
> However when I compare the "EXPLAIN QUERY PLAN" with a partial index vs. a
> normal index, SQLite
Hi,
I use a lot of indexes on fields that typically contain lots of NULLs, so
the WHERE NOT NULL partial indexing seems very useful.
However when I compare the "EXPLAIN QUERY PLAN" with a partial index vs. a
normal index, SQLite won't use the index to find Max(IndexedField) if it is
a partial ind
Hello Peter,
It's the generally the responsability of the callback implementor to test or
not each authorization, depending on her needs. See
https://sqlite.org/c3ref/set_authorizer.html
-- Allow user to run select statements, and read col1 of t1:
-- SQLITE_SELECT
-- SQLITE_READ t1
On 8 May 2017 at 14:35, Clemens Ladisch wrote:
> Rowan Worth wrote:
> > These days (the past 8 years?) at least there's the
> SQLITE_FCNTL_LAST_ERRNO
> > parameter to sqlite3_file_control() allowing the underlying cause to be
> > introspected, I just feel like it was a mistake to ever mask that c
10 matches
Mail list logo
