Re: [sqlite] Move to Github!!?

2017-12-25 Thread Jay Kreibich

> On Dec 25, 2017, at 12:24 PM, J. King  wrote:
> 
> SQLite source is managed in a Fossil (not Git)  repository, which is software 
> itself designed by Dr. Hipp and based on SQLite. GitHub would be an entirely 
> inappropriate venue. 
> 
> SQLite is also not open source software in the conventional sense. SQLite is 
> written by a small team of people, and outside contributions are far less 
> common than in most open source software. 


Indeed.  The core SQLite source code is free (as in beer, as in freedom), but 
its development is carefully controlled by Hwaci, the company responsible for 
employing SQLite developers.  Hwaci also owns the trademark to the name SQLite. 
Hwaci has several products, including extensions such as the SQLite encryption 
extensions, that are NOT free (as in beer, nor as in freedom).  The testing 
system used for SQLite, which represents a source base several times larger 
than the SQLite core, is also completely private.  Hosting such systems on 
Github would require a subscription fee and, frankly, why should they bother?

   -j

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


Re: [sqlite] Move to Github!!?

2017-12-25 Thread Jungle Boogie
On Mon 25 Dec 2017 11:49 PM, Shekhar Reddy wrote:
> Hi,
> 
> Is there any particular reason that the source is not moved to GitHub? I
> think that would reach more number of people there.
> 

So are you saying it would be the most used in the galaxy?
SQLite is the most used database engine in the world.[0]

[0] https://sqlite.org/about.html


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


[sqlite] SQLite 3.21 on IBM Mainframe - z/OS

2017-12-25 Thread Mario Bezzi

Hello,

SQLite 3.21 autoconf (sqlite-autoconf-321.zip) compiles and runs 
successfully on z/OS 2.2 with few minor modifications which I would like 
the developers to consider for integration into the code base.


Namely:

1 - In sqlite3.c, in the code section coming from tokenize.c, the EBCDIC 
version of the aiClass[] array defines codepoint 0x15 as class '27' 
(CC_ILLEGAL). In EBCDIC (both codepages 037 and 1047, the most common 
ones) 0x15 is actually NL (newline) and should be defined as class '7' 
CC_SPACE to allow the tokenizer to properly manage multi-line statements.


There are minor issues in the Makefile generated by ./configure:

2 - The ./configure process wrongly detects the presence of the posix 
fallocate function, which is not actually available ("checking for 
posix_fallocate... yes"), and sets -DHAVE_POSIX_FALLOCATE=1. It should 
be -DHAVE_POSIX_FALLOCATE=0. I don't know why this happens as I was not 
able to understand what the check does. I will be happy to help 
debugging it if guided.


3- In order to successfully compile sqlite3, the C compiler command 
(CC=..) should be changed from cc to xlc; the CFLAGS option should be 
set to "CFLAGS = -g -qFLOAT=IEEE -qstrict -qdll" and 
"-D_XOPEN_SOURCE=600" should be added to the current DEFS.


If needed I have a diff generated pach for 1) and another one for 2) 3) 
to make the required changes better understandable.


With these changes the process to build sqlite is as simple as:

1- Upload a non compressed tarball of the autoconf version of SQLite to 
a file in your OMVS environment (let say the file is called 
sqlite-autoconf-321.tar)


From your OMVS shell issue the following commands

2- pax -ofrom=iso8859-1,to=ibm-1047 -rf sqlite-autoconf-321.tar (the 
"to" codepage in the pax command must be set to your actual EBCDIC codepage)


3- ./configure --enable-dynamic-extension (I need this option myself but 
of course it is not mandatory)


4- for the time being manually apply the changes described above

5- make

Et voilà.

At the moment I am testing with the sqlite3 cli, and I can perform 
normal operations and load and use dynamic extensions.


I will keep testing and I will report other issues if any.

Hope this helps,

mario

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


[sqlite] FTS5 crash with NULL in snippet() function's 5th parameter

2017-12-25 Thread Tony Papadimitriou
(SQLite v3.21.0 with FTS5 enabled)

If instead of ‘’ (empty string) one uses NULL for the 5th parameter in the 
snippet() function it consistently crashes.

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


Re: [sqlite] Move to Github!!?

2017-12-25 Thread Keith Medcalf

Heavens forbid!

---
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 Shekhar Reddy
>Sent: Monday, 25 December, 2017 11:19
>To: sqlite-users@mailinglists.sqlite.org
>Subject: [sqlite] Move to Github!!?
>
>Hi,
>
>Is there any particular reason that the source is not moved to
>GitHub? I
>think that would reach more number of people there.
>
>Regards
>Shekhar
>___
>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] Ubuntu error with 3210000

2017-12-25 Thread petern
Are your linking switches the same in both release and debug?  In
particular, -ldl (dynamic libraries) ?

On Mon, Dec 25, 2017 at 5:31 AM, raanan barzel  wrote:

> With sqlite 3.21. embedded in my application, building on Windows (10,
> using VS 2017 Community) is error-free.
>
> However, building the same application on Ubuntu 16.04 in Release mode is
> error-free, while Debug mode produces errors:
>
> *** /usr/bin/ld: GCCDebug/sqlite3.o: undefined reference to symbol
> 'dlclose@@GLIBC_2.2.5'
>
> *** //lib/x86_64-linux-gnu/libdl.so.2: error adding symbols: DSO missing
> from command line
>
> Not being deeply involved with Linux, I have no idea what needs to be
> done. Any advice ?
>
> Thanks
>
>
> ---
> L'absence de virus dans ce courrier électronique a été vérifiée par le
> logiciel antivirus Avast.
> https://www.avast.com/antivirus
>
> ___
> 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] Move to Github!!?

2017-12-25 Thread Stephen Chrzanowski
As stated, SQLite is managed by Fossil, and Fossil is managed by SQLite.
(I think it was) Dr Hipp that stated that "Fossil is eating its own dog
food".

https://www.google.ca/search?q=eating+your+own+dog+food&ie=utf-8&oe=utf-8&client=firefox-b&gfe_rd=cr&dcr=0&ei=SENBWvCGOs6fXo7ynMAJ

https://www.investopedia.com/terms/e/eatyourowndogfood.asp


On Mon, Dec 25, 2017 at 1:24 PM, J. King  wrote:

> SQLite source is managed in a Fossil (not Git)  repository, which is
> software itself designed by Dr. Hipp and based on SQLite. GitHub would be
> an entirely inappropriate venue.
>
> SQLite is also not open source software in the conventional sense. SQLite
> is written by a small team of people, and outside contributions are far
> less common than in most open source software.
>
> On December 25, 2017 1:19:18 PM EST, Shekhar Reddy <
> shekharreddy.k...@gmail.com> wrote:
> >Hi,
> >
> >Is there any particular reason that the source is not moved to GitHub?
> >I
> >think that would reach more number of people there.
> >
> >Regards
> >Shekhar
> >___
> >sqlite-users mailing list
> >sqlite-users@mailinglists.sqlite.org
> >http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> ___
> 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] Move to Github!!?

2017-12-25 Thread J. King
SQLite source is managed in a Fossil (not Git)  repository, which is software 
itself designed by Dr. Hipp and based on SQLite. GitHub would be an entirely 
inappropriate venue. 

SQLite is also not open source software in the conventional sense. SQLite is 
written by a small team of people, and outside contributions are far less 
common than in most open source software. 

On December 25, 2017 1:19:18 PM EST, Shekhar Reddy 
 wrote:
>Hi,
>
>Is there any particular reason that the source is not moved to GitHub?
>I
>think that would reach more number of people there.
>
>Regards
>Shekhar
>___
>sqlite-users mailing list
>sqlite-users@mailinglists.sqlite.org
>http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


[sqlite] Move to Github!!?

2017-12-25 Thread Shekhar Reddy
Hi,

Is there any particular reason that the source is not moved to GitHub? I
think that would reach more number of people there.

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


[sqlite] LSM extension lsm_work

2017-12-25 Thread Josu Diaz de Arcaya
Hi all,

I am very happy with the inclusion of LSM extension in sqlite3's code base.
I have a question regarding
the merging of segments within the database.

I noticed that autowork enabled was not enough for keeping disk consumption
at bay, the generated database
was N times larger than the generated by sqlite3. Using lsm_work(db,1-1,0)
after every transaction seems to
mitigate this and the disk footprint of the db gets back to normal. This
seem to be explained by Mr. Kennedy
here http://www.sqlite.org/src4/doc/tip/www/lsmusr.wiki#explicit_scheduling

* What does exactly do lsm_work(db,1,-1,0) ? My assumption is that it
merges all the on disk segments into one larger
segment, is this correct?

* Doing this after every transactions of course takes some tool on
performance and everything goes significantly slower. What
is the best way of running lsm_work? in a separate thread like it is
mentioned in sqlite4's documentation?
http://www.sqlite.org/src4/doc/tip/www/lsmusr.wiki#explicit_scheduling

* Finally, can I call lsm_work less aggressively in terms of parameters? I
am worried about virtual memory consumption so I'd rather not do
a full lsm_work every time, something like.. merge until there are no more
elements with delete markers on it?

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


[sqlite] Ubuntu error with 3210000

2017-12-25 Thread raanan barzel
With sqlite 3.21. embedded in my application, building on Windows 
(10, using VS 2017 Community) is error-free.


However, building the same application on Ubuntu 16.04 in Release mode 
is error-free, while Debug mode produces errors:


*** /usr/bin/ld: GCCDebug/sqlite3.o: undefined reference to symbol 
'dlclose@@GLIBC_2.2.5'


*** //lib/x86_64-linux-gnu/libdl.so.2: error adding symbols: DSO missing 
from command line


Not being deeply involved with Linux, I have no idea what needs to be 
done. Any advice ?


Thanks


---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
https://www.avast.com/antivirus

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