Skip to content

Conversion of BSONTimstamp should not happen [DATAMONGO-1059] #1980

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
spring-projects-issues opened this issue Sep 24, 2014 · 2 comments
Closed
Assignees
Labels
type: bug A general bug

Comments

@spring-projects-issues
Copy link

John Butler opened DATAMONGO-1059 and commented

I have code that takes advantage of MongoDB's capability to assign the value of a BSONTimestamp server-side. This is done by inserting a DBObject whose first field is a "new BSONTimestamp()". However, Spring Data is not recognizing that BSONTimestamp is a MongoDB-specific class and is converting it to a BasicDBObject. This is file for the cases where this value is populated client-side but breaks when it is populated server-side.

Please see the "Timestamps" section of http://docs.mongodb.org/manual/reference/bson-types/


No further details from DATAMONGO-1059

@spring-projects-issues
Copy link
Author

John Butler commented

I believe this issue is OBE because MongoDB will now look at any first-level field.

https://jira.mongodb.org/browse/SERVER-15367

@christophstrobl
Copy link
Member

resolved via #579

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A general bug
Projects
None yet
Development

No branches or pull requests

3 participants