crdt

When a client application using Antidote crashes or has incorrect transaction handling, some or even many transactions can stay open. These transactions are never forcefully aborted by Antidote. This can potentially leave many txn-coordinator-fsms running forever.

For a database that should be deployed as a long-running system, this behavior is unacceptable. Transactions, that are not used anym

While implementing Increase operation(#12), I became curious about the updatedAt property of data type in json package.

I expected this for this property. For example,

err := doc.Update(func(root *proxy.ObjectProxy) error {
			root.SetNewText("k1")
				.Edit(0, 0, "ABCD")
			text := root.GetText("k1")
			u := text.UpdatedAt()
			assert.NotNil(t, u)
			return nil
	})

As

Jul	AUG	Sep
	25
2019	2020	2021

crdt

Here are 171 public repositories matching this topic...

amark / gun

orbitdb / orbit-db

yjs / yjs

lasp-lang / lasp

weaveworks / mesh

atom / teletype-crdt

AntidoteDB / antidote

peer-base / peer-pad

berty / berty

rust-crdt / rust-crdt

derekkraan / delta_crdt_ex

fthomas / crjdt

orbitdb / ipfs-log

peer-base / peer-base

archagon / crdt-playground

blindpad / blindpad

cudr / slate-collaborative

neurodrone / crdt

ljwagerfield / crdt

justin-db / JustinDB

ff-notes / ff

peer-base / js-delta-crdts

yorkie-team / yorkie

orbitdb / crdts

d6y / wootjs

okeuday / cpg

softindex / datakernel

berty / go-orbit-db

johnny-morrice / godless

DevResults / cevitxe

Improve this page

Add this topic to your repo