You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, i'm using MongoDB 3.4 and morphia 1.3 to test the new Decimal128 data type. I use to have a custom TypeConverter for my BigDecimals, they were stored on the database as strings.
So far i've disabled my custom converter, and updated the data directly on MongoDB. I can't make morphia save my BigDecimals as Decimal128. Inspecting the execution seems like the Mapper doesn't get the desired converter to BigDecimal, instead it uses the default Embedded Mapper.
Oh, dear. That's definitely a bug. A missing super constructor call. Turns out we tested all the conversion scenarios by invoking the converter directly and never tried round tripping that conversion in an entity. mea culpa.
Hello, i'm using MongoDB 3.4 and morphia 1.3 to test the new Decimal128 data type. I use to have a custom TypeConverter for my BigDecimals, they were stored on the database as strings.
So far i've disabled my custom converter, and updated the data directly on MongoDB. I can't make morphia save my BigDecimals as Decimal128. Inspecting the execution seems like the Mapper doesn't get the desired converter to BigDecimal, instead it uses the default Embedded Mapper.
The class for my test:
And a database
db.Foo.find()
:Am I missing some configuration for the conversion BigDecimal <-> Decimal128 work properly?
The text was updated successfully, but these errors were encountered: