|
|
|
|
|
|
See https://www.mongodb.com/blog/post/introducing-30-java-driver:
{quote}
So for users of the 2.x driver series that are upgrading to 3.0, the driver still has the
MongoClient.getDB("myDB") method and, although it has been deprecated, rest easy -- it won't be
removed in the 3.x series. The deprecation is intended to nudge new applications towards the
MongoDatabase/MongoCollection API, which is accessible via the new
MongoClient.getDatabase("myDB") method. This way we retain backwards compatibility while still
offering an improved API that users can migrate to at their own pace. - See more at:
https://www.mongodb.com/blog/post/introducing-30-java-driver#sthash.JDGalGNX.dpuf
{quote}
From https://github.com/hibernate/hibernate-ogm/pull/572:
{quote}
So at the moment we still use the deprecated MongoClient.getDB call. Not everything underneath is deprecated (I guess they wanted to keep the warnings down), but once you switch to MongoClient.getDatabase you are going down a whole rabbit hole of changes. As said, I am somewhere in the middle of this, but wanted to get this in first.
This is how CRUD works now - http://mongodb.github.io/mongo-java-driver/3.0/driver/reference/crud/. I guess DBObject was maybe wrong to list, but the changeset becomes quite large.
{quote}
|
|
|
|
|
|
