On 12 Jun 2012, at 12:06am, Brent Shifley <brentshif...@yahoo.com> wrote:
> So, if I understand things correctly, if I created said app, with associated > database, if I had identical databases on both iPads, and tracked all > transactions and used them to modify a third copy of the database, that this > might work? > > Uh, right. > > Since I am beginner programmer / beginner sql dude (can you tell I like a > challenge / pain) how would I store said transactions so that I can readily > post them against the third db? I'm actually warning you that unless you have a ton of experience you're going to get this wrong and lose data and have your users shouting at you. The question you asked is unsolved: nobody has found a good way to do it. Sorry. You can think of six solutions which look like they'll work and a professional programmer will find problems with all of them. However, since you mention iPads, you don't really need to synchronise copies of the database which have been kept separate from one-another. If you can rely on your iPads being connected to the internet you can use Apple's own iCloud system in realtime. Rather than wait until someone presses a 'synch' button, have changes show up on all iPads immediately. This gets rid of the problem of delayed synchronisation: all changes are made on all copies at once, and everyone sees them immediately. You'll find tools do to this are available to you as an iPad programmer. Though I recommend you tackle other aspects of your programming first: it's not simple to do iCloud programming and iPad programming itself isn't easy compared to simple ways of programming a computer. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
