At 11:58 31/08/2015, you wrote:
>---
>But the only sure way to prevent anyone else from installing its own
>authorizer is to change the function name in the SQLite library.
>---
That wouldn't really work under Windows: GetProcAddress can provide
access to a DLL function by index (ordinal
Dominique Devienne wrote:
> One annoyance with the authorizer approach is that you cannot "stack them"
Write your own authorizer that implements its own callback list.
But the only sure way to prevent anyone else from installing its own
authorizer is to change the function name in the SQLite
On Thu, Aug 27, 2015 at 4:21 PM, Dominique Devienne
wrote:
> On Thu, Aug 27, 2015 at 3:37 PM, Richard Hipp wrote:
>
>> On 8/27/15, Clemens Ladisch wrote:
>> > Dominique Devienne wrote:
>> >> how can we programatically reliably discover which (v)tables a view
>> >> accesses, staying in
On Thu, Aug 27, 2015 at 4:20 PM, Hick Gunter wrote:
> But you have to run the query as opposed to just parsing EXPLAIN
>
The doc says:
The authorizer callback is invoked as SQL statements are being compiled
by sqlite3_prepare() [and co.]
So the query to prepare is different indeed (drop
On Thu, Aug 27, 2015 at 3:37 PM, Richard Hipp wrote:
> On 8/27/15, Clemens Ladisch wrote:
> > Dominique Devienne wrote:
> >> how can we programatically reliably discover which (v)tables a view
> >> accesses, staying in documented behavior land?
> >
> > With an authorizer callback:
> >
On 27 Aug 2015, at 3:20pm, Hick Gunter wrote:
> But you have to run the query as opposed to just parsing EXPLAIN
You have to _prepare() it. You don't have to use _step() . Though I suppose
you should _finalize() it if you don't intend to use _step() .
Simon.
Dominique Devienne wrote:
> how can we programatically reliably discover which (v)tables a view
> accesses, staying in documented behavior land?
With an authorizer callback:
http://www.sqlite.org/c3ref/set_authorizer.html
Regards,
Clemens
But you have to run the query as opposed to just parsing EXPLAIN
-Urspr?ngliche Nachricht-
Von: Richard Hipp [mailto:drh at sqlite.org]
Gesendet: Donnerstag, 27. August 2015 15:37
An: General Discussion of SQLite Database
Betreff: Re: [sqlite] explain plan change between SQLite 3.8.3.1
On Thu, Aug 27, 2015 at 1:08 PM, Richard Hipp wrote:
> On 8/27/15, Dominique Devienne wrote:
> >
> > I understand that https://www.sqlite.org/opcode.html doesn't explicitly
> say
> > what VOpen's p4 column will contain, so I guess one could argue this is
> > undocumented behavior we should not
On 8/27/15, Clemens Ladisch wrote:
> Dominique Devienne wrote:
>> how can we programatically reliably discover which (v)tables a view
>> accesses, staying in documented behavior land?
>
> With an authorizer callback:
> http://www.sqlite.org/c3ref/set_authorizer.html
>
Clever! I was about to
Recently upgraded, and we ran into failures because references to vtables
(via opcode VOpen's p4 column) changed from vtab:module_ptr:vtable_ptr to
just vtab:vtable_ptr.
What was the intent behind this change?
How can code one determine the module the vtable is coming from now?
This is not a
On 8/27/15, Dominique Devienne wrote:
>
> I understand that https://www.sqlite.org/opcode.html doesn't explicitly say
> what VOpen's p4 column will contain, so I guess one could argue this is
> undocumented behavior we should not rely on,
On needn't argue this; it is explicitly stated in
12 matches
Mail list logo
