MongoDB Embedded Reference Duplicate Error
up vote
0
down vote
favorite
I am new to MongoDB
, and coming from Sql database systems. I am confused about embedded reference's of mongodb.
I use Java Spring Framework and MongoRepository
interface of Spring. I have a class (User
) that annotated with @Document
and has a String field (id
) of annotated @Indexed(unique = true)
. I have second class (Device
) that has an embedded User
object in it. It's like many-to-one relation (many devices may belong one user), however when I try to save second device with same User, application throws en error E11000 duplicate key error collection: test.device index: user.id dup key: { : "5a8549fbeed7ae612d6a10d1" }.
I tried making User
object in Devices
reference (with @DBRef
annotation), and @Indexed(unique = false)
, I could manage to save two devices. However, I dont want to use reference document, embedding document will be better.
I just wonder, is my approach wrong? Or my configuration was wrong?
java spring mongodb
add a comment |
up vote
0
down vote
favorite
I am new to MongoDB
, and coming from Sql database systems. I am confused about embedded reference's of mongodb.
I use Java Spring Framework and MongoRepository
interface of Spring. I have a class (User
) that annotated with @Document
and has a String field (id
) of annotated @Indexed(unique = true)
. I have second class (Device
) that has an embedded User
object in it. It's like many-to-one relation (many devices may belong one user), however when I try to save second device with same User, application throws en error E11000 duplicate key error collection: test.device index: user.id dup key: { : "5a8549fbeed7ae612d6a10d1" }.
I tried making User
object in Devices
reference (with @DBRef
annotation), and @Indexed(unique = false)
, I could manage to save two devices. However, I dont want to use reference document, embedding document will be better.
I just wonder, is my approach wrong? Or my configuration was wrong?
java spring mongodb
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am new to MongoDB
, and coming from Sql database systems. I am confused about embedded reference's of mongodb.
I use Java Spring Framework and MongoRepository
interface of Spring. I have a class (User
) that annotated with @Document
and has a String field (id
) of annotated @Indexed(unique = true)
. I have second class (Device
) that has an embedded User
object in it. It's like many-to-one relation (many devices may belong one user), however when I try to save second device with same User, application throws en error E11000 duplicate key error collection: test.device index: user.id dup key: { : "5a8549fbeed7ae612d6a10d1" }.
I tried making User
object in Devices
reference (with @DBRef
annotation), and @Indexed(unique = false)
, I could manage to save two devices. However, I dont want to use reference document, embedding document will be better.
I just wonder, is my approach wrong? Or my configuration was wrong?
java spring mongodb
I am new to MongoDB
, and coming from Sql database systems. I am confused about embedded reference's of mongodb.
I use Java Spring Framework and MongoRepository
interface of Spring. I have a class (User
) that annotated with @Document
and has a String field (id
) of annotated @Indexed(unique = true)
. I have second class (Device
) that has an embedded User
object in it. It's like many-to-one relation (many devices may belong one user), however when I try to save second device with same User, application throws en error E11000 duplicate key error collection: test.device index: user.id dup key: { : "5a8549fbeed7ae612d6a10d1" }.
I tried making User
object in Devices
reference (with @DBRef
annotation), and @Indexed(unique = false)
, I could manage to save two devices. However, I dont want to use reference document, embedding document will be better.
I just wonder, is my approach wrong? Or my configuration was wrong?
java spring mongodb
java spring mongodb
edited Feb 15 at 9:10
pvpkiran
11.4k42141
11.4k42141
asked Feb 15 at 9:08
Black Glix
151317
151317
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
You can use @Transient
annotation over Device.user
field if the user information is not relevant. If you need the User information in Device document try to use the User.id
field (sql approach).
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
You can use @Transient
annotation over Device.user
field if the user information is not relevant. If you need the User information in Device document try to use the User.id
field (sql approach).
add a comment |
up vote
0
down vote
You can use @Transient
annotation over Device.user
field if the user information is not relevant. If you need the User information in Device document try to use the User.id
field (sql approach).
add a comment |
up vote
0
down vote
up vote
0
down vote
You can use @Transient
annotation over Device.user
field if the user information is not relevant. If you need the User information in Device document try to use the User.id
field (sql approach).
You can use @Transient
annotation over Device.user
field if the user information is not relevant. If you need the User information in Device document try to use the User.id
field (sql approach).
edited Nov 22 at 15:30
L.Butz
1,3241137
1,3241137
answered Nov 22 at 14:53
David Cadena
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f48803451%2fmongodb-embedded-reference-duplicate-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown