jus...@postgresql.org wrote...
On 2014-11-06 03:12, nicolas riesch wrote:
There is a bug in some Linux implementations (RedHat9 is the
canonical
example) that prevents fcntl() locks created by one thread from being
modified in a different thread.
As a data point, "Red Hat 9" is incredibly
On 6 Nov 2014, at 3:13am, Andrei Yakimov wrote:
> Problem is incorrect journal file, which is created on system reboot.
> Reproduce this condition relativity simple:
>
> step 1: we open db
> step 2: write/update something to db.
> step 3: switch journal to memory
> step 4: write/update some
On Thu, Nov 6, 2014 at 2:15 PM, Michael Suodenjoki <
michael.suodenj...@intrasoft-intl.dk> wrote:
> Hi,
>
> I'm a bit disoriented by the following result - here using SQLite command
> shell:
>
> sqlite> .version
> SQLite 3.8.6 2014-08-15 11:46:33 9491ba7d738528f168657adb43a198238abde19e
> sqlite>
Hi,
I'm a bit disoriented by the following result - here using SQLite command shell:
sqlite> .version
SQLite 3.8.6 2014-08-15 11:46:33 9491ba7d738528f168657adb43a198238abde19e
sqlite> CREATE TABLE test( col TEXT COLLATE NOCASE );
sqlite> INSERT INTO test VALUES ('b'), ('A'), ('B'), ('a');
sqlite>
Hi,
I have using Sqlite for my small embedded projects for quite a while.
Recently we found a condition where is simple select all does not operate
properly.
Problem is incorrect journal file, which is created on system reboot.
Reproduce this condition relativity simple:
step 1: we open db
step
Hi there,
Since virtual tables were recenty mentioned in the thread "SQLite as a
meta database" , I take this opportunity to announce that the lastest
version of the DBD::SQLite driver for Perl now has support for virtual
tables (see https://metacpan.org/pod/DBD::SQLite ).
This means that y
On Thu, Nov 6, 2014 at 7:51 AM, wrote:
> On 2014-11-06 03:12, nicolas riesch wrote:
>
>
>> There is a bug in some Linux implementations (RedHat9 is the canonical
>> example) that prevents fcntl() locks created by one thread from being
>> modified in a different thread.
>>
>
> As a data point,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/05/2014 02:05 PM, nicolas riesch wrote:
> This means that EACH SUCCESSIVE function in the sequence above can
> be processed on a DIFFERENT OS THREAD.
That works just fine with SQLite, with one caveat. You should also
make sure the wrapper itsel
Thank you Jan.
On Thu, Nov 6, 2014 at 7:46 AM, Jan Nijtmans wrote:
> 2014-11-06 1:14 GMT+01:00 E. Timothy Uy :
> > Hi, I noticed that the ignore-glob for sqlite is empty. Is it just
> because
> > fossil does not transfer this information? What should I be using?
>
> I'm using the "ignore-glob" v
2014-11-06 1:14 GMT+01:00 E. Timothy Uy :
> Hi, I noticed that the ignore-glob for sqlite is empty. Is it just because
> fossil does not transfer this information? What should I be using?
I'm using the "ignore-glob" versioned setting below.
Regards,
Jan Nijtmans
$ cat .fossil-settings/
On 2014-11-06 03:12, nicolas riesch wrote:
There is a bug in some Linux implementations (RedHat9 is the
canonical
example) that prevents fcntl() locks created by one thread from being
modified in a different thread.
As a data point, "Red Hat 9" is incredibly ancient, from 2003:
http://en
On Thu, Nov 6, 2014 at 4:12 AM, nicolas riesch
wrote:
> http://www.sqlite.org/cvstrac/wiki?p=MultiThreading
Be aware that the cvstrac pages are all historical, possibly outdated, and
no longer maintained.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"
On Thu, Nov 6, 2014 at 1:14 AM, E. Timothy Uy wrote:
> Hi, I noticed that the ignore-glob for sqlite is empty. Is it just because
> fossil does not transfer this information? What should I be using?
>
http://sqlite.org/src/dir
sqlite doesn't have a .fossil-settings dir, i.e. no versioned settin
SQLite allow to attach more database at session level.
Perhaps here you could find a solution
Il 06/nov/2014 09:31 "Hugo Mercier" ha scritto:
> Le 05/11/2014 23:08, Simon Slavin a écrit :
> >
> > On 5 Nov 2014, at 9:28pm, Edward Lau wrote:
> >
> >> Maybe some time in the future a version 4 be s
xCreate should specify "CREATE TABLE x (label TEXT);" which assumes that rowid
is the implicit index
xBestIndex needs to return:
1) cost = 1, index = 0 if a single constraint -1 (rowid) and operation
EQ is provided (assuming the record position can be calculated from the index)
2) cost
Le 05/11/2014 23:08, Simon Slavin a écrit :
>
> On 5 Nov 2014, at 9:28pm, Edward Lau wrote:
>
>> Maybe some time in the future a version 4 be started that incorporates many
>> new advancement in the industry. Version 3 can still be continued for
>> backwards compatibility and version 4 will b
16 matches
Mail list logo