On Thu, Apr 17, 2014 at 5:13 PM, Richard Hipp <d...@sqlite.org> wrote:
> That's a very interesting idea. That's not something for a weekend hack >> (it would require bigger changes), >> >> > Would this really require a big change? > i kinda made an conservative guess there ;). Seems like about all you have to do is COMMIT after each round-trip to > the server, rather than waiting to COMMIT at the very end. Or, just COMMIT > instead of ROLLBACK after getting a server timeout. > Would that be a valid strategy? Couldn't we end up with a partial state which we can't work from until the pull finishes to completion? -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
