Update doesn't keep key

[Flavio Oliveira]

Hi,

I am trying to update a document (com.novemberain/monger "2.0.0-rc1")

Original document

{

    "_id" : ObjectId("538590c9fa3994a54c5bc4f0"),

    "round" : 3,

    "score" : 1

}

(mc/update table "teste" {:round 3} {:score 10} {:multi false})))

Updated

{

    "_id" : ObjectId("538590c9fa3994a54c5bc4f0"),

    "score" : NumberLong(10)

}

soce has been updated but ... What happened to the round field?

Regards, Flavio

[Michael Klishin]

2014-05-28 11:37 GMT+04:00 Flavio Oliveira <flav...@gmail.com>:

(mc/update table "teste" {:round 3} {:score 10} {:multi false})))

Updated

{

    "_id" : ObjectId("538590c9fa3994a54c5bc4f0"),

    "score" : NumberLong(10)

}

soce has been updated but ... What happened to the round field?

Update by default replaces the entire document. You need to use atomic modifiers:

http://clojuremongodb.info/articles/updating.html

http://clojuremongodb.info/articles/updating.html#using_set_operator
--
MK

http://github.com/michaelklishin
http://twitter.com/michaelklishin

[Samuel Lê]

Hi,

I had the same issue as Flavio. I am wondering, for the function update, shouldn't {$set {:key value}} be the default?

Cheers,
Sam

[Michael Klishin]

 On 30 July 2014 at 07:15:58, Samuel Lê (samu...@gmail.com) wrote:
> > I had the same issue as Flavio. I am wondering, for the function
> update, shouldn't {$set {:key value}} be the default?

This would make Monger's defaults incompatible with the rest of the MongoDB
drivers and MongoDB shell.
--
@michaelklishin, github.com/michaelklishin