Thus said Richard Hipp on Thu, 17 Apr 2014 11:13:38 -0400: > Would this really require a big change? 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.
I think Fossil already does the latter; or I just read the code wrong. At the end of client_sync() it calls db_end_transaction(0): http://www.fossil-scm.org/index.html/artifact/dace4194506b2ea7?ln=1936 Which will cause a COMMIT to happen unless there are errors (with commit hooks): http://www.fossil-scm.org/index.html/artifact/17595c8a94256a4d?ln=162,185 Am I wrong? Andy -- TAI64 timestamp: 400000005352ed3d _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users