summaryrefslogtreecommitdiff
path: root/docs/leap-commit-template.README
diff options
context:
space:
mode:
authorVictor Shyba <victor.shyba@gmail.com>2015-09-19 14:25:30 -0300
committerVictor Shyba <victor.shyba@gmail.com>2015-09-28 16:52:53 -0300
commitc4c280e12bf70dd41183d2d2ffbba200a45d0247 (patch)
tree992d4344f1e7d58b6fe1057c0a7e367d59eab3d6 /docs/leap-commit-template.README
parent7b1591e3d561aa6525318235e702eebeb6708560 (diff)
[feat] handle DatabaseDoesNotExist during sync
This error raises while getting info on target (or server) replica. On previous implementation there was nothing to do here, but now that we have db creation in place this error should be handled just like u1db original implementation. The reason is that db creation occurs during sync exchange, but before this we try to ask for info and the code that checks for info raises an error that will be used to signal the client that a database will be created and that it must save the replica uid returned by server, after sync exchange (where we send/fetch documents).
Diffstat (limited to 'docs/leap-commit-template.README')
0 files changed, 0 insertions, 0 deletions