ump
> in; I'll make further inquiries tomorrow.
>
> -John Daily
> Technical Evangelist
>
> On May 19, 2013, at 7:29 PM, Jeremy Ong wrote:
>
>> For automatic conflict resolution, often times, the easiest thing to do is
>> impose a Last Write Wins policy.
hought in the past will jump
> in; I'll make further inquiries tomorrow.
>
> -John Daily
> Technical Evangelist
>
> On May 19, 2013, at 7:29 PM, Jeremy Ong wrote:
>
> For automatic conflict resolution, often times, the easiest thing to do is
> impose a Last Write Wins p
Daily
Technical Evangelist
On May 19, 2013, at 7:29 PM, Jeremy Ong wrote:
> For automatic conflict resolution, often times, the easiest thing to do is
> impose a Last Write Wins policy.
>
> However, in certain circumstances, First Write Wins makes more sense. For
> example, suppo
For automatic conflict resolution, often times, the easiest thing to do is
impose a Last Write Wins policy.
However, in certain circumstances, First Write Wins makes more sense. For
example, suppose you are handling user creation. Creating a single user
will populate values for two keys:
User Id
