-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.9.3
-
Component/s: API
-
Labels:
-
Environment:$ uname -a
Linux 3.5.0-24-generic #37-Ubuntu SMP Thu Feb 7 01:50:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
$ mongo --version
MongoDB shell version: 2.0.6
$ mongod --version
db version v2.0.6, pdfile version 4.5
Tue Feb 12 18:53:04 git version: nogitversion
$ java -version
java version "1.7.0_13"
Java(TM) SE Runtime Environment (build 1.7.0_13-b20)
Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
$ uname -a Linux 3.5.0-24-generic #37-Ubuntu SMP Thu Feb 7 01:50:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ mongo --version MongoDB shell version: 2.0.6 $ mongod --version db version v2.0.6, pdfile version 4.5 Tue Feb 12 18:53:04 git version: nogitversion $ java -version java version "1.7.0_13" Java(TM) SE Runtime Environment (build 1.7.0_13-b20) Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
Hi,
I encounter strange behaviour regarding the writeResult.getN() returned value.
The first save to a DBCollection seems to be failing, writeResult.getN() being != 1, but in fact, it does save the object, a subsequent find() proves it (see the attache test class, the method theTest).
After a seemingly failled save, a second save actually return writeResult.getN() being == 1 (see theSecondTest).
Did I do/understood something wrong?
Thanks for your precious help!
Brice.