On Wed, Mar 4, 2015 at 8:02 AM, Even Rouault
wrote:
> Norman,
>
> >
> > the aim is to sync data between masters as per -
> > http://dataprotocols.org/couchdb-replication/ An example would be using
> > GDAL in QGIS and going offline to edit data and then coming back online,
> > the user would need
Norman,
>
> the aim is to sync data between masters as per -
> http://dataprotocols.org/couchdb-replication/ An example would be using
> GDAL in QGIS and going offline to edit data and then coming back online,
> the user would need to synchronize the dataset. As replication is a core
> part of Co
Hi Even,
the aim is to sync data between masters as per -
http://dataprotocols.org/couchdb-replication/ An example would be using
GDAL in QGIS and going offline to edit data and then coming back online,
the user would need to synchronize the dataset. As replication is a core
part of CouchDB I woul
Norman,
I'm not familiar with what this "sync" is about, so please bear with the naive
questions.
Is it to synchronize all masters between them ?
Why GetFeature() and/or not at the first GetNextFeature(), or at database
opening ?
What is the persistence you mention, and what is the connexion wit
Hi,
I am looking to add sync to the GDAL CouchDB driver. I would rather not add
additional API functions to do this but to wrap it up in the
usual GetFeature call. The first call to GetFeature would initiate a sync,
but thoughts on this are appreciated.
Sync is a useful function that is a key dif
