2015-12-27 21:51 GMT+01:00 Cecil Westerhof :
> invocation), you should use SQLite binding to some real program language
>
>> (perl, tcl, python,...) instead of sh and sqlite3.
>
>
> ?Well, for just checking if a database is locked I think it is good
> enough. But I also wrote a Java program for
Hello !
I don't know how I could not find it before, I searched for json in my
browser pages (but probably not on the main page because yes it's there).
But I also now searched again using https://www.sqlite.org/search?q=json and
it doesn't appear on the results page, probably the full text
> Le 28 d?c. 2015 ? 17:13, Domingo Alvarez Duarte dev.dadbiz.es> a ?crit :
>
> I think that the json1 functions are important enough to deserve a place on
> the top level documentation page https://www.sqlite.org/docs.html !
And there is one such link there on that page.
JSON SQL Functions
Hello !
I just needed to work with json but didn't remember all the json1 available
functions and it's parameters so I went to https://www.sqlite.org/docs.html
and did not found any mention to then, then I did a search
https://www.sqlite.org/search?q=json and again nothing about then I remember
On 12/28/2015 05:08 AM, Olivier Mascia wrote:
> Hello,
>
> I'm referring to paragraph 1.3 of https://www.sqlite.org/fileformat2.html
> about the Lock-Byte page.
>
> From what I read, I understand those 2^9 bytes at offset 2^30, should they
> exist, are set aside, untouched by SQLite nor the
On 12/28/15, Olivier Mascia wrote:
>> Le 28 d?c. 2015 ? 17:13, Domingo Alvarez Duarte
>> a ?crit :
>>
>> I think that the json1 functions are important enough to deserve a place
>> on
>> the top level documentation page https://www.sqlite.org/docs.html !
>
> And there is one such link there on
On 12/25/15, Valentin Davydov wrote:
>
> It would be desirable to improve algorithm of INTEGRITY_CHECK pragma.
> Presently it is generally useless for indexed databases which don't fit
> entirely in RAM (and which usually need checking much strongly than
> smaller ones).
>
For each row of each
On Fri, Dec 25, 2015 at 12:51:55PM +, Simon Slavin wrote:
>
> On 25 Dec 2015, at 12:39pm, Valentin Davydov
> wrote:
>
> > It would be desirable to improve algorithm of INTEGRITY_CHECK pragma.
> > Presently it is generally useless for indexed databases which don't fit
> > entirely in RAM
> Le 28 d?c. 2015 ? 08:27, Dan Kennedy a ?crit :
>
> It's because (at least historically - may have changed?) win32 does not
> support advisory locks. So if you take an EXCLUSIVE lock on a range of bytes
> no other process can read them. This is different from Unix, where all locks
> are
On 28 Dec 2015, at 9:01am, Valentin Davydov wrote:
> As far as I understand, INTEGRITY_CHECK simply iterates over the records
> (of tables and indices) one by one in some arbitrary order. So, if the
> database is too big to fit in the available memory (sqlite's own cache,
> system file cache
On 28 Dec 2015, at 2:02am, Igor Korot wrote:
> Is it possible to save the SQLite DB file whose name contains some Unicode
> characters?
The filename you pass to sqlite3_open_v2() should be encoded in UTF-8.
The filename you pass to sqlite3_open16() should be encoded in UTF-16.
Both of these
On 2015-12-24 6:21 PM, Stephen Chrzanowski wrote:
> One thing I would suggest, if you're looking to add and delete columns
> dynamically is not to worry about the order of the columns in the database,
> but, have a second table hanging around that remembers the specified order
> the user wants to
12 matches
Mail list logo
