Any more thoughts on that?
I like Sanne's approach but it means that people not use @Column will very
often have id and _id and of course that we need to maintain secondary indexes.
On 10 avr. 2012, at 16:26, Sanne Grinovero wrote:
> Why should we not rely on the flexibility of the object/physic
Why should we not rely on the flexibility of the object/physical
mapping we normally provide to relational database users?
Specifically, would it be possible to use "javax.persistence.Column"
to have the user specify how the @Id attribute should be mapped in the
"physical" MongoDB "schema" ?
If t
My DBA background tells me 'do not do thing behind the back of rou db' : I
shall use the second strategy.
But I am not sure what is the exact contract around _id column from the
MongoDb devs.
Niko
2012/4/6 Emmanuel Bernard
> I would like to discuss the problem of _id in MongoDB and how to map
I would like to discuss the problem of _id in MongoDB and how to map that in
Hibernate OGM.
MongoDB is a bit psycho-rigid in how it uniquely identifies a document. A
special property named _id is used for that and must be unique across a
collection. It is also strongly recommended to let MongoD
