Hi,
Is it possible to protect sqlite3 db file with password protection in Linux.
Techi
Isaac Goldberg wrote:
> I'm seeing that EXPLAIN QUERY PLAN returns SEARCH instead of SCAN when
> using min() or max(). For example:
>
> sqlite> create table t(a int, b int);
> sqlite> explain query plan select min(b) from t;
> 0|0|0|SEARCH TABLE t
>
> Why is this a SEARCH instead of a SCAN?
On 2 Sep 2015, at 2:00pm, Simon Slavin wrote:
> Because there's no convenient index.
Whoops. Sorry. Ignore me. Pay attention to Clemens.
Simon.
On 1 Sep 2015, at 7:40am, Isaac Goldberg wrote:
> I'm seeing that EXPLAIN QUERY PLAN returns SEARCH instead of SCAN when
> using min() or max(). For example:
>
> sqlite> create table t(a int, b int);
>> sqlite> explain query plan select min(b) from t;
>> 0|0|0|SEARCH TABLE t
>
> Why is this a
The documentation is correct after all. The table name is not in the 4th
parameter, but in the 6th parameter. The content of the 6th parameter is
covered by "The 6th parameter to the authorizer callback is the name of
the inner-most trigger or view that is responsible for the access
Yes. There are free and paid options for this. For instance:
https://www.sqlite.org/see/doc/trunk/www/index.wiki
https://www.zetetic.net/sqlcipher/
On Wed, Sep 2, 2015 at 9:36 AM, techi eth wrote:
> Hi,
>
> Is it possible to protect sqlite3 db file with password protection in
> Linux.
>
>
>> On Sep 1, 2015, at 9:37 AM, Roger Binns wrote:
>>
>> On 08/31/2015 11:28 PM, Jeff M wrote:
>> All my bad -- I'm fessing up.
>
> Can you tell us how you found the root causes of the problems? It
> would be nice to know what tools and techniques worked.
> Roger
Since you asked...
The crash
7 matches
Mail list logo
