In a database, read-write conflicts are equally important. One might attempt to map database mobility onto the file system to leverage the Coda work. There are two strategies. Each tuple could be mapped into a file, or each table could be mapped into a file. However, neither solution is desirable.
Mobile clients win by replicating data.
Since disconnection is expected, clients can hoard the data they expect to use. The mobile clients, ideally, should be able to locally commit modifications to the database and later reintegrate those changes. This reintegration could be managed at various levels of granularity. However, the tuple-level seems to fine and the table level seems to coarse. DBMate uses an intermediate level of granularity called a fragment .