Re: [sqlite] Bug in sqlite: "View with UNION ALL and limit in subquery" (v 3.28.0)

[Richard Hipp]

Thank you for the report.  The problem is now fixed on trunk.

Ticket: https://www.sqlite.org/src/info/c41afac34f15781f
Fix: https://www.sqlite.org/src/info/523b42371122d9e1

On 5/29/19, Marco Foit  wrote:
> Dear SQLite Developers,
>
> I just noticed the following bug in SQLite version 3.28.0:
>
> 
>
> create table t AS values (1), (2);
>
> .print "select with correct output  ..."
> select * from ( select * from t limit 1 )
> union all
> select * from t
> ;
>
> .print "same select leads to incorrect result when used inside view ..."
> create view v as
> select * from ( select * from t limit 1 )
> union all
> select * from t
> ;
>
> select * from v;
>
> 
>
>
> * How to reproduce:
> Run the attached SQL code from a shell with:
>
>   sqlite3 < sqlite-bug.sql
>
>
> * Expected result:
> Both queries should yield the following output:
> 1
> 1
> 2
>
> * What did go wrong:
> The second query yields to the output:
> 1
>
>
> It seems that the limit clause in the compound select when used inside a
> view is used for the overall result set and not for the subquery.
>
>
> In the hope that this might help others.
> Thank you very much for your hard work!
>
>
> Cheers,
> Marco
>
>
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>


-- 
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite4 version

[Warren Young]

On May 29, 2019, at 7:12 AM, Mike King  wrote:
> 
> Would it make sense for DRH to rename V4 to something else? For the
> uninitiated it’s not always apparent that V3 is what you should be using.

drh appears to use major version number changes to mean “breaking file format 
change,” rather than just “major new version.”  Calling those now-terminated 
experiments “SQLite v4” was a way of saying that the file format was open to 
backwards-incompatible change for the first time since v2, which was something 
like 15 years ago now.

So, when drh says they aren’t going forward on the lines of development 
previously published as “SQLite 4” he’s saying that the current SQLite file 
format is expected to endure as-is for the foreseeable future.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] How to set access permissions to protect a database file?

[Peter da Silva]

This is what the UNIX group ID and the set-group-id capability is for.

You make the files readable (or read and write) by a group (mode 640 or
660).

You make the program that controls access to the files set-group-id to that
group.

You may need a small "C" wrapper program to run the script set-group-id
depending on the version of UNIX and security settings. Allowing scripts to
run set-group-id has at times been violently controversial, and I have not
bothered to track teh state of teh art.

On Mon, May 27, 2019 at 8:37 AM Richard Damon 
wrote:

> On 5/27/19 9:16 AM, Simon Slavin wrote:
> > On 27 May 2019, at 3:33am, Adrian Ho  wrote:
> >
> >> The OP wants *all users* to be able to update (write) the DB via the
> Tcl script reading_room.tcl, but *not* by (say) running the SQLite shell or
> something else. In your setup, as long as a specific user has write
> permissions, *every program* the user runs can write to the DB.
> > Some work in this thread has been because the file is a SQLite
> database.  But it's not really a SQLite question.  It's more about the
> access/permissions model of Debian 9.  What OP wants can be reduced to a
> simpler situation:
> >
> > "I have a text file.  It's on a computer running Debian 9.  I want to
> make sure that this text file can be read/written by multiple people, but
> that it can be read/written only using this program I wrote."
> >
> > I've never used Debian so I can't solve the problem.  But from what
> little I remember of Linux, one solution is to create a special account for
> that one operation, and set up that account in a non-standard way.
>
> Actually, It can be an SQLite question, as another way to solve the base
> problem is to do something to the database so that only 'authorized'
> applications can access/modify it. One way to do that is to use the SEE
> extension and encrypt the database. If you do that then you no longer
> have the equivalent of a 'text file', so unauthorized applications can't
> access the file.
>
> It isn't perfect protection, because someone still will have the ability
> to delete/overwrite the file, to protect from that seems to need the
> protection method you describe, but if you are only trying to protect
> against Murphy, and not Machiavelli (as the saying goes) it may be a
> viable, and portable, solution.
>
> --
> Richard Damon
>
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Bug in sqlite: "View with UNION ALL and limit in subquery" (v 3.28.0)

[Marco Foit]

Dear SQLite Developers,

I just noticed the following bug in SQLite version 3.28.0:



create table t AS values (1), (2);

.print "select with correct output  ..."
select * from ( select * from t limit 1 )
union all
select * from t
;

.print "same select leads to incorrect result when used inside view ..."
create view v as
select * from ( select * from t limit 1 )
union all
select * from t
;

select * from v;




* How to reproduce:
Run the attached SQL code from a shell with:

sqlite3 < sqlite-bug.sql


* Expected result:
Both queries should yield the following output:
1
1
2

* What did go wrong:
The second query yields to the output:
1


It seems that the limit clause in the compound select when used inside a 
view is used for the overall result set and not for the subquery.



In the hope that this might help others.
Thank you very much for your hard work!


Cheers,
Marco


___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite4 version

[Mario Bezzi]

On top of https://sqlite.org/src4/doc/trunk/www/index.wiki, the statement

"/All development work on SQLite has ended." /should hopefully be/
/

/"///All development work on SQLite4 has ended."//

:-)

Thank you,

mario//
//

On 5/29/19 3:17 PM, Simon Slavin wrote:

On 29 May 2019, at 2:12pm, Mike King  wrote:


Would it make sense for DRH to rename V4 to something else?

It might be helpful to put a note at the top of


___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite4 version

[Simon Slavin]

On 29 May 2019, at 2:12pm, Mike King  wrote:

> Would it make sense for DRH to rename V4 to something else?

It might be helpful to put a note at the top of


___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite4 version

[Simon Slavin]

On 29 May 2019, at 2:02pm, Warren Young  wrote:

> On May 29, 2019, at 6:16 AM, Simon Slavin  wrote:
> 
>> There may one day be a release of SQLite4
> 
> It doesn’t look like it: https://sqlite.org/src4/info/c0b7f14c0976ed5e

Right.  I was considering a 'new' SQLite4 with new ideas in.  Unless the dev 
team is going to miss that name out and call it SQLite5.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite4 version

[Mike King]

Would it make sense for DRH to rename V4 to something else? For the
uninitiated it’s not always apparent that V3 is what you should be using.

Cheers

On Wed, 29 May 2019 at 14:03, Warren Young  wrote:

> On May 29, 2019, at 6:16 AM, Simon Slavin  wrote:
> >
> > There may one day be a release of SQLite4
>
> It doesn’t look like it: https://sqlite.org/src4/info/c0b7f14c0976ed5e
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite4 version

[Donald Griggs]

Hello, Mittal,

Do you have a particular problem that you perceive would be solved by
sqlite4, and not by sqlite3, or were you simply wanting the "latest" sqlite
version?

>
>
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite4 version

[Warren Young]

On May 29, 2019, at 6:16 AM, Simon Slavin  wrote:
> 
> There may one day be a release of SQLite4

It doesn’t look like it: https://sqlite.org/src4/info/c0b7f14c0976ed5e
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite4 version

[Simon Slavin]

On 29 May 2019, at 7:21am, Mittal, Pradeep  wrote:

> I am new to SQLite and looking for SQLite version which supports the SQLite4 
> interfaces and implementation.

There has never been a release version of SQLite4.  SQLite4 is a testbed for 
new ideas and new features.  Some features which proved useful have been 
integrated into SQLite3.  Other features have been rejected.

There may one day be a release of SQLite4, which people outside the development 
team can use.  But that has not happened yet.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] I am unable to build sqlite3 on windows. Possible errors in https://sqlite.org/src/doc/trunk/README.md

[Keith Medcalf]

D:\Source\SQLite3 contains the fossil checkout of trunk
D:\Source\Bld is an empty directory

D:\Source\Bld>nmake -f ..\sqlite3\makefile.msc sqlite3.c TOP=..\sqlite3
... for the rest of the targets you want

In other words, you point to the makefile.msc wherever it may be found, and set 
TOP= to the directory which is the top of the distribution, and the results are 
scribbled into the current directory and below ...

---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a 
lot about anticipated traffic volume.

>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of Craig Delancy
>Sent: Tuesday, 28 May, 2019 21:43
>To: sqlite-users@mailinglists.sqlite.org
>Subject: [sqlite] I am unable to build sqlite3 on windows. Possible
>errors in https://sqlite.org/src/doc/trunk/README.md
>
>I am unable to successfully build SQLite3 following your
>instructions:
>
>"Using MSVC
>On Windows, all applicable build products can be compiled with MSVC.
>First open the command prompt window associated with the desired
>compiler version (e.g. "Developer Command Prompt for VS2013"). Next,
>use NMAKE with the provided "Makefile.msc" to build one of the
>supported targets.
>
>For example:
>
>mkdir bld
>cd bld
>nmake /f Makefile.msc TOP=..\sqlite
>nmake /f Makefile.msc sqlite3.c TOP=..\sqlite
>nmake /f Makefile.msc sqlite3.dll TOP=..\sqlite
>nmake /f Makefile.msc sqlite3.exe TOP=..\sqlite
>nmake /f Makefile.msc test TOP=..\sqlite
>There are several build options that can be set via the NMAKE command
>line. For example, to build for WinRT, simply add "FOR_WINRT=1"
>argument to the "sqlite3.dll" command line above. When debugging into
>the SQLite code, adding the "DEBUG=1" argument to one of the above
>command lines is recommended.
>
>SQLite does not require Tcl to run, but a Tcl installation is
>required by the makefiles (including those for MSVC). SQLite contains
>a lot of generated code and Tcl is used to do much of that code
>generation."
>
>Specifically, if I try to nmake while inside the newly created bld
>foler, the makefile is not found because that folder is currently
>empty. Perhaps there is a missing "cd .." prior to the first nmake
>line?
>
>However, if I test that, it still does not build. The following is
>what results:
>
>sqlite3.c
>sqlite3.c(19711): error C2065: 'OPFLG_INITIALIZER': undeclared
>identifier
>sqlite3.c(19711): error C2099: initializer is not a constant
>sqlite3.c(76038): error C2065: 'OP_Init': undeclared identifier
>sqlite3.c(76263): error C2065: 'OP_Goto': undeclared identifier
>sqlite3.c(76270): error C2065: 'OP_String8': undeclared identifier
>sqlite3.c(76292): error C2065: 'OP_Null': undeclared identifier
>sqlite3.c(76292): error C2065: 'OP_String8': undeclared identifier
>sqlite3.c(76294): error C2065: 'OP_Integer': undeclared identifier
>sqlite3.c(76299): error C2065: 'OP_ResultRow': undeclared identifier
>sqlite3.c(76384): error C2065: 'OP_Explain': undeclared identifier
>sqlite3.c(76412): error C2065: 'OP_ParseSchema': undeclared
>identifier
>sqlite3.c(76439): error C2065: 'OP_EndCoroutine': undeclared
>identifier
>sqlite3.c(76739): error C2065: 'SQLITE_MX_JUMP_OPCODE': undeclared
>identifier
>sqlite3.c(76743): error C2065: 'OP_Transaction': undeclared
>identifier
>sqlite3.c(76747): error C2065: 'OP_AutoCommit': undeclared identifier
>sqlite3.c(76748): error C2065: 'OP_Savepoint': undeclared identifier
>sqlite3.c(76753): error C2065: 'OP_Checkpoint': undeclared identifier
>sqlite3.c(76755): error C2065: 'OP_Vacuum': undeclared identifier
>sqlite3.c(76756): error C2065: 'OP_JournalMode': undeclared
>identifier
>sqlite3.c(76761): error C2065: 'OP_Next': undeclared identifier
>sqlite3.c(76762): error C2065: 'OP_SorterNext': undeclared identifier
>sqlite3.c(76771): error C2065: 'OP_Prev': undeclared identifier
>sqlite3.c(76781): error C2065: 'OP_VUpdate': undeclared identifier
>sqlite3.c(76785): error C2065: 'OP_VFilter': undeclared identifier
>sqlite3.c(76743): error C2051: case expression not constant
>sqlite3.c(76747): error C2051: case expression not constant
>sqlite3.c(76748): error C2051: case expression not constant
>sqlite3.c(76753): error C2051: case expression not constant
>sqlite3.c(76755): error C2051: case expression not constant
>sqlite3.c(76756): error C2051: case expression not constant
>sqlite3.c(76761): error C2051: case expression not constant
>sqlite3.c(76762): error C2051: case expression not constant
>sqlite3.c(76771): error C2051: case expression not constant
>sqlite3.c(76781): error C2051: case expression not constant
>sqlite3.c(76785): error C2051: case expression not constant
>sqlite3.c(76920): error C2065: 'OPFLG_JUMP': undeclared identifier
>sqlite3.c(77109): error C2065: 'OP_Noop': undeclared identifier
>sqlite3.c(77938): error C2065: 'OP_Explain': undeclared identifier
>sqlite3.c(77939): error C2065: 'OP_Init': undeclared identifier
>sqlite3.c(80901): 

[sqlite] LSM INT key problem

[ingo]

Both SQlite.exe and lsm.dll are compiled on Win10 with Mingwin64.
Lsm by copying sqlite3.h and sqlite3ext.h to the lsm1 directory and
then: make lsm.so TCCX="gcc -g -O2" and rename to lsm.dll

Creating a lsm table with an INT key results in the following:

SQLite version 3.28.0 2019-04-16 19:49:53
[...]
sqlite> .load lsm
sqlite> CREATE VIRTUAL TABLE test USING lsm1 (
   ...>   'test.lsm', idx, INT, d
   ...> );
Error: key type should be INT, TEXT, or BLOB

sqlite> CREATE VIRTUAL TABLE test USING lsm1 (
   ...>   'test.lsm', idx, INTEGER, d
   ...> );
Error: key type should be INT, TEXT, or BLOB

Using TXT or BLOB there is no error. Did I go wrong somewhere?

Ingo

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] SQLite4 version

[Mittal, Pradeep]

Hi,

I am new to SQLite and looking for SQLite version which supports the SQLite4 
interfaces and implementation. Please suggest me the released version of SQLite 
which support SQLIte4. Also please let me know, if there is any license 
requirements for the same.

If there is any web portal for SQLite4 documentation and examples, please let 
me know.

Any help in this regards, will be highly appreciated.

Regards,
Pradeep
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] I am unable to build sqlite3 on windows. Possible errors in https://sqlite.org/src/doc/trunk/README.md

[Craig Delancy]

I am unable to successfully build SQLite3 following your instructions:

"Using MSVC
On Windows, all applicable build products can be compiled with MSVC. First open 
the command prompt window associated with the desired compiler version (e.g. 
"Developer Command Prompt for VS2013"). Next, use NMAKE with the provided 
"Makefile.msc" to build one of the supported targets.

For example:

mkdir bld
cd bld
nmake /f Makefile.msc TOP=..\sqlite
nmake /f Makefile.msc sqlite3.c TOP=..\sqlite
nmake /f Makefile.msc sqlite3.dll TOP=..\sqlite
nmake /f Makefile.msc sqlite3.exe TOP=..\sqlite
nmake /f Makefile.msc test TOP=..\sqlite
There are several build options that can be set via the NMAKE command line. For 
example, to build for WinRT, simply add "FOR_WINRT=1" argument to the 
"sqlite3.dll" command line above. When debugging into the SQLite code, adding 
the "DEBUG=1" argument to one of the above command lines is recommended.

SQLite does not require Tcl to run, but a Tcl installation is required by the 
makefiles (including those for MSVC). SQLite contains a lot of generated code 
and Tcl is used to do much of that code generation."

Specifically, if I try to nmake while inside the newly created bld foler, the 
makefile is not found because that folder is currently empty. Perhaps there is 
a missing "cd .." prior to the first nmake line?

However, if I test that, it still does not build. The following is what results:

sqlite3.c
sqlite3.c(19711): error C2065: 'OPFLG_INITIALIZER': undeclared identifier
sqlite3.c(19711): error C2099: initializer is not a constant
sqlite3.c(76038): error C2065: 'OP_Init': undeclared identifier
sqlite3.c(76263): error C2065: 'OP_Goto': undeclared identifier
sqlite3.c(76270): error C2065: 'OP_String8': undeclared identifier
sqlite3.c(76292): error C2065: 'OP_Null': undeclared identifier
sqlite3.c(76292): error C2065: 'OP_String8': undeclared identifier
sqlite3.c(76294): error C2065: 'OP_Integer': undeclared identifier
sqlite3.c(76299): error C2065: 'OP_ResultRow': undeclared identifier
sqlite3.c(76384): error C2065: 'OP_Explain': undeclared identifier
sqlite3.c(76412): error C2065: 'OP_ParseSchema': undeclared identifier
sqlite3.c(76439): error C2065: 'OP_EndCoroutine': undeclared identifier
sqlite3.c(76739): error C2065: 'SQLITE_MX_JUMP_OPCODE': undeclared identifier
sqlite3.c(76743): error C2065: 'OP_Transaction': undeclared identifier
sqlite3.c(76747): error C2065: 'OP_AutoCommit': undeclared identifier
sqlite3.c(76748): error C2065: 'OP_Savepoint': undeclared identifier
sqlite3.c(76753): error C2065: 'OP_Checkpoint': undeclared identifier
sqlite3.c(76755): error C2065: 'OP_Vacuum': undeclared identifier
sqlite3.c(76756): error C2065: 'OP_JournalMode': undeclared identifier
sqlite3.c(76761): error C2065: 'OP_Next': undeclared identifier
sqlite3.c(76762): error C2065: 'OP_SorterNext': undeclared identifier
sqlite3.c(76771): error C2065: 'OP_Prev': undeclared identifier
sqlite3.c(76781): error C2065: 'OP_VUpdate': undeclared identifier
sqlite3.c(76785): error C2065: 'OP_VFilter': undeclared identifier
sqlite3.c(76743): error C2051: case expression not constant
sqlite3.c(76747): error C2051: case expression not constant
sqlite3.c(76748): error C2051: case expression not constant
sqlite3.c(76753): error C2051: case expression not constant
sqlite3.c(76755): error C2051: case expression not constant
sqlite3.c(76756): error C2051: case expression not constant
sqlite3.c(76761): error C2051: case expression not constant
sqlite3.c(76762): error C2051: case expression not constant
sqlite3.c(76771): error C2051: case expression not constant
sqlite3.c(76781): error C2051: case expression not constant
sqlite3.c(76785): error C2051: case expression not constant
sqlite3.c(76920): error C2065: 'OPFLG_JUMP': undeclared identifier
sqlite3.c(77109): error C2065: 'OP_Noop': undeclared identifier
sqlite3.c(77938): error C2065: 'OP_Explain': undeclared identifier
sqlite3.c(77939): error C2065: 'OP_Init': undeclared identifier
sqlite3.c(80901): error C2065: 'OP_PureFunc': undeclared identifier
sqlite3.c(84179): error C2065: 'OP_Goto': undeclared identifier
sqlite3.c(84221): error C2065: 'OP_Gosub': undeclared identifier
sqlite3.c(84242): error C2065: 'OP_Return': undeclared identifier
sqlite3.c(84261): error C2065: 'OP_InitCoroutine': undeclared identifier
sqlite3.c(84281): error C2065: 'OP_EndCoroutine': undeclared identifier
sqlite3.c(84307): error C2065: 'OP_Yield': undeclared identifier
sqlite3.c(84327): error C2065: 'OP_HaltIfNull': undeclared identifier
sqlite3.c(84366): error C2065: 'OP_Halt': undeclared identifier
sqlite3.c(84432): error C2065: 'OP_Integer': undeclared identifier
sqlite3.c(8): error C2065: 'OP_Int64': undeclared identifier
sqlite3.c(84458): error C2065: 'OP_Real': undeclared identifier
sqlite3.c(84475): error C2065: 'OP_String8': undeclared identifier
sqlite3.c(84478): error C2065: 'OP_String': undeclared identifier
sqlite3.c(84518): error C2065: 

Re: [sqlite] Making blob as a sqlite database.

[Keith Medcalf]

https://sqlite.org/c3ref/deserialize.html
https://sqlite.org/c3ref/serialize.html

---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a 
lot about anticipated traffic volume.

>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of Mohd Radzi Ibrahim
>Sent: Tuesday, 28 May, 2019 21:23
>To: SQLite mailing list
>Subject: Re: [sqlite] Making blob as a sqlite database.
>
>Hi Don,
>I am working on sales and stock management systems where all outlets
>run on
>it's own local database. I was thinking of a solution for all outlets
>to
>backup to central server and perhaps thru web interface do some
>queries on
>the backup database. I know postgres has binary interface that allow
>read/write to blob record which is quite promising to have a vfs
>system
>that can just store database in that record.
>
>But it seems that the blob in SQLite could not do that.
>
>
>On Tue, Apr 30, 2019 at 10:44 PM Don V Nielsen
>
>wrote:
>
>> Sorry to bother, Mohd. What is your use case? I mentioned this to
>> developers around me and they are intrigued. You are storing a
>database
>> file as blob in a database? We are curious as to the application. I
>am
>> assuming the database being stored is a collection of sensor or
>event data?
>>
>> On Fri, Apr 26, 2019 at 5:48 PM Mohd Radzi Ibrahim
>
>> wrote:
>>
>> > Hi, is there a vfs that could be used to open a blob column as a
>> database?
>> >
>> >
>> > thanks.
>> >
>> > Radzi.
>> > ___
>> > sqlite-users mailing list
>> > sqlite-users@mailinglists.sqlite.org
>> > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-
>users
>> >
>> ___
>> sqlite-users mailing list
>> sqlite-users@mailinglists.sqlite.org
>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-
>users
>>
>___
>sqlite-users mailing list
>sqlite-users@mailinglists.sqlite.org
>http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users



___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users