On 30 Jul 2011, at 11:31pm, Alexey Pechnikov wrote:
> There are no conflicts! Two versions are two _different_ versions of the row.
> Simple copy _all_ un-exists rows by SQL query with attached database
> or simple script
> http://sqlite.mobigroup.ru/wiki?name=sqlite3-rdiff
> It can be included
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2011 03:31 PM, Alexey Pechnikov wrote:
> There are no conflicts!
If you have multiple masters then incompatible changes can be made to the
same data.
> Two versions are two _different_ versions of the row.
ie you have a conflict.
> On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2011 03:12 PM, Simon Slavin wrote:
> Conflict resolution is so hard it's sometimes impossible.
CouchDB does it well. The vast majority of the time there are no conflicts.
When there is a conflict it picks one contender (something like
2011/7/31 Roger Binns :
> It takes more than a few lines of SQL. You've also got to be careful how
> you write data (result is a DAG), you need replication code and you need
> conflict resolution code.
There are no conflicts! Two versions are two _different_ versions of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2011 02:29 PM, Mr. Puneet Kishor wrote:
> could you please tell what this other "JSON database server product" was?
MongoDB.
A major difference between MongoDB and CouchDB is how they store data.
CouchDB uses an append only structure - data
On 30 Jul 2011, at 10:57pm, Roger Binns wrote:
> On 07/30/2011 01:43 PM, Alexey Pechnikov wrote:
>> Multi-master replication can be easy with correct data structures.
>
> It takes more than a few lines of SQL. You've also got to be careful how
> you write data (result is a DAG), you need
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2011 01:43 PM, Alexey Pechnikov wrote:
> Multi-master replication can be easy with correct data structures.
It takes more than a few lines of SQL. You've also got to be careful how
you write data (result is a DAG), you need replication code
On Jul 31, 2011, at 6:04 AM, Roger Binns wrote:
> A different JSON database server product used 4GB and 6
> minutes and I never bothered optimising for it. Perhaps more shocking is
> that the other product would usually answer unindexed queries faster than
> CouchDB did with indices, mostly
Multi-master replication can be easy with correct data structures.
As example:
CREATE TABLE test
(
id INTEGER PRIMARY KEY ON CONFLICT REPLACE,
cid INTEGER UNIQUE -- equal to test_record.id
);
CREATE TABLE test_record
(
id INTEGER NOT NULL, -- record version id
rid INTEGER PRIMARY
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2011 12:24 PM, Max Vlasov wrote:
> so CouchDB will be a server solution
My (year old) experience with CouchDB has been that it is a poor database,
especially in what they consider "large" amounts of data. I was working
with a dataset of 10
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2011 10:45 AM, Alexey Pechnikov wrote:
> Very interesting annonce:
> http://www.couchbase.com/press-releases/unql-query-language
It is rather difficult to work out from the spec pages how it differs from
regular SQL. Personally I think it
On Sat, Jul 30, 2011 at 9:45 PM, Alexey Pechnikov wrote:
> Very interesting annonce:
> http://www.couchbase.com/press-releases/unql-query-language
>
>
Thanks for the info, very interesting indeed.
After some reading at http://www.unqlspec.org I'd rather think Richard
Very interesting annonce:
http://www.couchbase.com/press-releases/unql-query-language
--
Best regards, Alexey Pechnikov.
http://pechnikov.tel/
___
sqlite-users mailing list
sqlite-users@sqlite.org
> From: "Jay A. Kreibich"
> Date: July 29, 2011 6:23:24 AM PDT
> Subject: Re: [sqlite] Exclusive locking mode not working as expected?
>
> On many OSes and most filesystems, file locking is advisory, not
> mandatory. File locks are essentially OS maintained atomic flags
>
NewsGroup gmane.comp.db.sqlite.general
Subject .. Loading Data
Date . 2011-07-28
Post_By .. Daniel Spain
Edit_By .. Stanley C. Kitching
I added some white space and new-line characters
to Daniel's original post using a first pass
through Python and a
On 07/30/2011 12:19 PM, Dan Kennedy wrote:
> On 07/30/2011 04:45 AM, Gabor Cselle wrote:
>> Just a heads-up that we just posted an update to the benchmarks:
>> - No more superfluous index on the primary key
>> - WAL turned on with auto-checkpointing every 4096 pages
>>
>>
I ran a few tests. First the 2 tests from Rev 45. Then NORMAL sync, and
finally bump the cache up to what sqlite3 needs vs an arbitrary 100M. I think
the question should be how well does it perform in cache -- not necessarily how
much cache it needs. How much cache is just a comparision of
2011/7/30 Gabor Cselle :
> Just a heads-up that we just posted an update to the benchmarks:
> - No more superfluous index on the primary key
> - WAL turned on with auto-checkpointing every 4096 pages
You may use "PRAGMA synchronous = NORMAL" instead of "PRAGMA
synchronous =
18 matches
Mail list logo