Re: [sqlite] Will SQLite supports UnQL?

On Jul 31, 2011, at 12:58 PM, Simon Slavin wrote: > These two go together. Multi-master replication (one example of which is a > document store) is relatively easy. Datestamp every value (document) and > whichever one has the lastest date is the one you want. I hear that a lot, but

[sqlite] Sqlite-Wal file location

Hello, Inorder to suit the needs of my embedded device, I have changed the location of the .db-wal file from the location of the db file to tmpfs. Does sqlite make assumptions(persistence etc) based on the location of the file ? ___ sqlite-users

Re: [sqlite] How to convert a database with FTS2 to FTS3/4?

On Fri, Jul 29, 2011 at 10:33 PM, Ray Van Dolson wrote: > sqlite newbie here.  I have a sqlite3 database that was built using the > FTS2 module.  As such I get errors about the non-existent fts2 module > when attempting to query the data. > > Is there a way to convert/migrate

Re: [sqlite] Will SQLite supports UnQL?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/31/2011 12:58 PM, Simon Slavin wrote: > Datestamp every value (document) and whichever one has the lastest date is > the one you want. That isn't always the correct approach and requires clocks to be synchronized - something that is

Re: [sqlite] Will SQLite supports UnQL?

On 31 Jul 2011, at 8:50pm, Roger Binns wrote: > Multi-master replication is always hard > which is why it is so rare. > > The simplicity of the document model is because you put everything relevant > into a single item which typically matches the programmer's idea of an object. These two go

Re: [sqlite] Will SQLite supports UnQL?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/31/2011 11:53 AM, Alexey Pechnikov wrote: > A normalized database can't be easy replicated and checked. That is what makes these databases (variously document oriented or JSON) so attractive. There is no rigid schema and no two documents need

Re: [sqlite] Will SQLite supports UnQL?

Roger, thanks for good explanation and examples of the multi-master replication problems. But I think a conflict-resolutions strategies may be independent. And checking logical data integrity is needed for systems without replication too. This checking is not a part of the replication but it's

Re: [sqlite] SQLITE_OMIT_UTF16

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/31/2011 09:14 AM, Baruch Burstein wrote: > I can use Linux if it makes it easier, This is how I build which also works with grabbing the current development snapshots. After extracting the relevant archive: make TOP=. -f Makefile.linux-gcc

Re: [sqlite] SQLITE_OMIT_UTF16

On Sun, Jul 31, 2011 at 5:24 PM, Kees Nuyt wrote: > and I don't run MSWindows. > I can use Linux if it makes it easier, but I gather from the rest of your mail that you still won't be able to help me. Thank you anyway for trying. ___

Re: [sqlite] Will SQLite supports UnQL?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/31/2011 07:49 AM, Simon Slavin wrote: > neither of them can enter the new price into the system, they have to each > enter the price change, You cannot get conflicts if both "users" are talking to the same server - I can explain why if you

Re: [sqlite] Will SQLite supports UnQL?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Any database system can be nonsensical. If you have multiple people editing prices for the same item even with a single instance database you can have the wrong final answer. But that is a procedural and business issue, not a technological one.

Re: [sqlite] Will SQLite supports UnQL?

On 31 Jul 2011, at 3:42pm, Roger Binns wrote: > Scroll down to the bottom third of this document to the Conflicts section > where you get blurb (but not technical details) about it: > > http://couchdb.apache.org/docs/overview.html Okay. So CouchDB requires intentional data entry and uses

Re: [sqlite] Will SQLite supports UnQL?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/30/2011 11:33 PM, Alexey Pechnikov wrote: > You write extra code to find and resolve CouchDB replication conflicts but you > are speak about "do not have to write extra code". One of these > approvals is false! Not quite and it was deliberate

Re: [sqlite] SQLITE_OMIT_UTF16

On Sun, 31 Jul 2011 11:30:05 +0300, Baruch Burstein wrote: > I am using the amalgamation embedded in my program. I am a little unfamiliar > with configure / make as I have almost always used IDEs that handle these > things (I think). I don't know what the

Re: [sqlite] Will SQLite supports UnQL?

On 31 Jul 2011, at 8:07am, Alexey Pechnikov wrote: > 2011/7/31 Simon Slavin : >> Right. So if a customer orders one of my products they'll be presented with >> two different costs and pick the one they like. Great system. > > You customers have edit privilegies to you

Re: [sqlite] SQLITE_OMIT_UTF16

I am using the amalgamation embedded in my program. I am a little unfamiliar with configure / make as I have almost always used IDEs that handle these things (I think). I don't know what the sqlite-autoconf-3070701.tar.gz file you referred to is. Can you give me an example of what exactly I would

Re: [sqlite] SQLITE_OMIT_UTF16

On Sun, 31 Jul 2011 09:54:29 +0300, Baruch Burstein wrote: > Can you refer me to instructions on building the amalgamation? The SQLite > website only says something like "Download the source, hand edit the make > file, and run make". Very unhelpful as I don't know what to

Re: [sqlite] Will SQLite supports UnQL?

2011/7/31 Simon Slavin : > Right.  So if a customer orders one of my products they'll be presented with > two different costs and pick the one they like.  Great system. You customers have edit privilegies to you prices?! It's not the replication problem of cource. As

Re: [sqlite] SQLITE_OMIT_UTF16

Can you refer me to instructions on building the amalgamation? The SQLite website only says something like "Download the source, hand edit the make file, and run make". Very unhelpful as I don't know what to do with the make file. On Thu, Jul 28, 2011 at 9:35 PM, Roger Binns

Re: [sqlite] Will SQLite supports UnQL?

2011/7/31 Roger Binns : > My original point was that CouchDB has multi-master replication builtin - > you do not have to write extra code or do anything special. and > You can > programmatically find conflicts and then it is up to you how to resolve them > since only your