Stored object property name mismatch
See original GitHub issueHi! Consider simple data class data class User(val isActive:Boolean)
. When stored it being saved as {active: true}
. isActive
becomes active
. It looks odd, it’s not very predictable and I always should check what should I write in the query in this case. Is it a bug or maybe it’s configurable behavior? Thanks!
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Working with objects - JavaScript - MDN Web Docs - Mozilla
An object is a collection of properties, and a property is an association between a name (or key) and a value. A property's...
Read more >ObjectStore Properties
For an ObjectStore object, this property specifies the location within the database. If this property is set during creation of the object store,...
Read more >Create and edit properties
Object type: if creating a property, select the object that will store the property. ... This is the name of the property as...
Read more >Objects
Create an empty object user . · Add the property name with the value John . · Add the property surname with the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes @outring KMongoConfiguration.registerBsonModule
HTH
Thanks, @zigzago. Is there any way to configure kmongo’s ObjectMapper instance from the outside?