News for hackers. Stuff that matters.
Re:Noms – A versioned, forkable, syncable database by rwmj on Sunday October 16, 2016 @06:51AM (#12718023)
There's quite a dramatic claim on the website, "merge [...] changes efficiently and correctly days, weeks, or years later." How does that work? For example if you have two records saying userid 3's name is "ann" and userid 3's name is "jane", I don't see how you could merge those without extra information or human input.
Re:Noms – A versioned, forkable, syncable database by aboodman on Sunday October 16, 2016 @11:19AM (#12718970)
The claim on the website is not meant to suggest that any two changes can be automatically merged. I will try to clarify that.

The world contains logical conflicts because physical constraints mean that processes can operate disconnected from each other. No database can wave that away.

Noms will automatically, efficiently, and correctly merge changes that don't logically conflict. Which is a pretty cool and unique property in a database.

If any conflicts are found, there is a callback to user software to perform a resolution.

More info in the documentation:

https://godoc.org/github.com/attic-labs/noms/go/merge

Re:Noms – A versioned, forkable, syncable database by nradov on Sunday October 16, 2016 @11:57AM (#12719180)
IBM Domino (aka Lotus Notes) has been automatically, efficiently, and correctly merging changes that don't logically conflict since 1989. How is the functionality in Noms unique?
Re:Noms – A versioned, forkable, syncable database by aardvark179 on Sunday October 16, 2016 @08:05AM (#12718239)
It's a very hard problem to solve. The best you can really manage is to automatically merge non-conflicting changes, and defining what is a conflicting change will require some extra knowledge if you have multiple tables with relations between them.

For extra fun try doing this with geographic data and try merging geometry changes correctly.

Re:Noms – A versioned, forkable, syncable database by striking on Sunday October 16, 2016 @09:49AM (#12718563)
Well, hopefully you're not just using an incrementing user id field. Twitter's Snowflake format is much closer to "definitely unique". So then you have a very simple set, which you could very simply merge with other sets. So that might help you get started with merging those pieces of data.

But I agree, there are certain kinds of data that you can't so efficiently merge. Your best bet is to try to adapt it into some sort of known, proven CRDT. (Dunno how you do that with this database, haven't really read up on it.)