Closed GoogleCodeExporter closed 9 years ago
Thank you, we will check it later.
Original comment by iwind....@gmail.com
on 31 Mar 2011 at 1:38
maybe we should use bson data type:
http://bsonspec.org/
Original comment by iwind....@gmail.com
on 31 Mar 2011 at 2:11
In MongoDB, it always be double, so i changed integer and float options to
double.
Original comment by iwind....@gmail.com
on 1 Apr 2011 at 3:50
The following patch addresses the issue with int/long/float support for the
RockMongo in the following manner:
- values of type int32 are displayed as NumberInt(...)
- values of type int64 are displayed as NumberLong(...)
- values of type double are always displayed with the decimal point (e.g. 12
will display as 12.0)
The patch adds/fixes the following parts:
- Integer / Long types are added as valid field options for New / Modify field
- JSON / array serialization works with int/long types now
- rename of int/long field doesn't change it's type to double (it was a bug
before)
To support the int64 type, the MongoDB settings for native int64 and int64 as
object were enabled (per http://derickrethans.nl/64bit-ints-in-mongodb.html )
Patch applies cleanly to the current SVN version.
Please review.
Thanks,
Kyryl
Original comment by kyryl.bilokurov
on 9 Mar 2012 at 12:34
Attachments:
A very important fix - without it the update functions corrupt the data with
invalid values.
Is this going to be integrated in the next release?
Any reason why it wasn't part of the new v1.1.1?
Thank you.
Original comment by ar...@scene53.com
on 6 May 2012 at 11:12
Yes, i will integrate it into next release, if it does work.
Original comment by iwind....@gmail.com
on 7 May 2012 at 6:03
Kyryl Bilokurov's patch does not work on MongoDB 1.8.x, always warn:
JS Error: ReferenceError: NumberInt is not defined nofile_b:6
Original comment by iwind....@gmail.com
on 7 May 2012 at 8:53
Fixed in RockMongo v1.1.2 http://rockmongo.com/?action=downloads
Although there is a display bug (caused by PHP).
Original comment by iwind....@gmail.com
on 7 May 2012 at 10:53
Original issue reported on code.google.com by
nowind...@gmail.com
on 30 Mar 2011 at 5:11