On Sat, Mar 17, 2018 at 11:42 PM, Marco Bambini wrote:
> with a bit of work you can use the authorize api in order to know when an
> access to a non existing table is performed.
> https://sqlite.org/c3ref/set_authorizer.html
Interesting work-around, if that works. I.e.
Philippe,
with a bit of work you can use the authorize api in order to know when an
access to a non existing table is performed.
https://sqlite.org/c3ref/set_authorizer.html
Hope this helps.
--
Marco Bambini
http://www.sqlabs.com
http://twitter.com/sqlabs
> On 17 Mar 2018, at 15:53, Philippe
On 3/17/18, Philippe Riand wrote:
> We are using virtual tables to provide an SQL access to our data set and
> this works very well. But we have potentially "a lot” of virtual tables,
> with some even yet unknown when we start the DB. We’d like to create them
> lazily, on
We are using virtual tables to provide an SQL access to our data set and this
works very well. But we have potentially "a lot” of virtual tables, with some
even yet unknown when we start the DB. We’d like to create them lazily, on
first access.
Is there a hook we can use so when an SQL
4 matches
Mail list logo