Mongo c#: Upserting is creating a new document instead












0














I have the following object



class Dog{
[BsonId]
[BsonRepresentation(BsonType.ObjectId)]
[BsonIgnoreIfDefault]
[BsonIgnoreIfNull]
public string Id { get; set; }

public string Owner {get; set;}
}


the following code is failing to upsert the document, instead it creates a new document and because of that I have some problems, sure, I could delete the old document before inserting this one, but that would also be 2 queries instead of 1 query.



var result = await
collection.FindOneAndReplaceAsync(
Builders<Dog>.Filter.Eq("owner","bill"),
updateddog,
new FindOneAndReplaceOptions{
ReturnDocument = ReturnDocument.After,
IsUpsert = true});


I have read somewhere that behave like that because the C# driver serialize the Id field, and then it is used to match the object, but since default Id is used then the object is not matched, I tried as suggested to Ignore the Id if it is null or default, but that don't work










share|improve this question


















  • 1




    What about Eq("Owner", "bill") or even Eq(x => x.Owner, "bill")? Bottom line is that if it's new then it did not "match" anything. And the most likely reason here is the difference in case for the property names.
    – Neil Lunn
    Nov 12 at 9:00










  • makes no difference at all.
    – UberFace
    Nov 12 at 9:17










  • I want to match 2 fields, both of those are not Id, and then update all other fields (except "Id") and to create a new object if it does not exists: Upserting a object with another based on 2 fields that are not Id.
    – UberFace
    Nov 12 at 9:18










  • So show a document you expect to be updating then. As already stated the rules are pretty basic. 1. Do I match something, then update. 2. If I don't then insert a new document. So new means "not found" in all cases. Forget thinking about "Id Serialization", because that's just wrong and not the reason here. It's all about the "query" needing to actually find something. And it's clearly not matching when something new gets created.
    – Neil Lunn
    Nov 12 at 9:19


















0














I have the following object



class Dog{
[BsonId]
[BsonRepresentation(BsonType.ObjectId)]
[BsonIgnoreIfDefault]
[BsonIgnoreIfNull]
public string Id { get; set; }

public string Owner {get; set;}
}


the following code is failing to upsert the document, instead it creates a new document and because of that I have some problems, sure, I could delete the old document before inserting this one, but that would also be 2 queries instead of 1 query.



var result = await
collection.FindOneAndReplaceAsync(
Builders<Dog>.Filter.Eq("owner","bill"),
updateddog,
new FindOneAndReplaceOptions{
ReturnDocument = ReturnDocument.After,
IsUpsert = true});


I have read somewhere that behave like that because the C# driver serialize the Id field, and then it is used to match the object, but since default Id is used then the object is not matched, I tried as suggested to Ignore the Id if it is null or default, but that don't work










share|improve this question


















  • 1




    What about Eq("Owner", "bill") or even Eq(x => x.Owner, "bill")? Bottom line is that if it's new then it did not "match" anything. And the most likely reason here is the difference in case for the property names.
    – Neil Lunn
    Nov 12 at 9:00










  • makes no difference at all.
    – UberFace
    Nov 12 at 9:17










  • I want to match 2 fields, both of those are not Id, and then update all other fields (except "Id") and to create a new object if it does not exists: Upserting a object with another based on 2 fields that are not Id.
    – UberFace
    Nov 12 at 9:18










  • So show a document you expect to be updating then. As already stated the rules are pretty basic. 1. Do I match something, then update. 2. If I don't then insert a new document. So new means "not found" in all cases. Forget thinking about "Id Serialization", because that's just wrong and not the reason here. It's all about the "query" needing to actually find something. And it's clearly not matching when something new gets created.
    – Neil Lunn
    Nov 12 at 9:19
















0












0








0







I have the following object



class Dog{
[BsonId]
[BsonRepresentation(BsonType.ObjectId)]
[BsonIgnoreIfDefault]
[BsonIgnoreIfNull]
public string Id { get; set; }

public string Owner {get; set;}
}


the following code is failing to upsert the document, instead it creates a new document and because of that I have some problems, sure, I could delete the old document before inserting this one, but that would also be 2 queries instead of 1 query.



var result = await
collection.FindOneAndReplaceAsync(
Builders<Dog>.Filter.Eq("owner","bill"),
updateddog,
new FindOneAndReplaceOptions{
ReturnDocument = ReturnDocument.After,
IsUpsert = true});


I have read somewhere that behave like that because the C# driver serialize the Id field, and then it is used to match the object, but since default Id is used then the object is not matched, I tried as suggested to Ignore the Id if it is null or default, but that don't work










share|improve this question













I have the following object



class Dog{
[BsonId]
[BsonRepresentation(BsonType.ObjectId)]
[BsonIgnoreIfDefault]
[BsonIgnoreIfNull]
public string Id { get; set; }

public string Owner {get; set;}
}


the following code is failing to upsert the document, instead it creates a new document and because of that I have some problems, sure, I could delete the old document before inserting this one, but that would also be 2 queries instead of 1 query.



var result = await
collection.FindOneAndReplaceAsync(
Builders<Dog>.Filter.Eq("owner","bill"),
updateddog,
new FindOneAndReplaceOptions{
ReturnDocument = ReturnDocument.After,
IsUpsert = true});


I have read somewhere that behave like that because the C# driver serialize the Id field, and then it is used to match the object, but since default Id is used then the object is not matched, I tried as suggested to Ignore the Id if it is null or default, but that don't work







c# mongodb






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 12 at 8:57









UberFace

948




948








  • 1




    What about Eq("Owner", "bill") or even Eq(x => x.Owner, "bill")? Bottom line is that if it's new then it did not "match" anything. And the most likely reason here is the difference in case for the property names.
    – Neil Lunn
    Nov 12 at 9:00










  • makes no difference at all.
    – UberFace
    Nov 12 at 9:17










  • I want to match 2 fields, both of those are not Id, and then update all other fields (except "Id") and to create a new object if it does not exists: Upserting a object with another based on 2 fields that are not Id.
    – UberFace
    Nov 12 at 9:18










  • So show a document you expect to be updating then. As already stated the rules are pretty basic. 1. Do I match something, then update. 2. If I don't then insert a new document. So new means "not found" in all cases. Forget thinking about "Id Serialization", because that's just wrong and not the reason here. It's all about the "query" needing to actually find something. And it's clearly not matching when something new gets created.
    – Neil Lunn
    Nov 12 at 9:19
















  • 1




    What about Eq("Owner", "bill") or even Eq(x => x.Owner, "bill")? Bottom line is that if it's new then it did not "match" anything. And the most likely reason here is the difference in case for the property names.
    – Neil Lunn
    Nov 12 at 9:00










  • makes no difference at all.
    – UberFace
    Nov 12 at 9:17










  • I want to match 2 fields, both of those are not Id, and then update all other fields (except "Id") and to create a new object if it does not exists: Upserting a object with another based on 2 fields that are not Id.
    – UberFace
    Nov 12 at 9:18










  • So show a document you expect to be updating then. As already stated the rules are pretty basic. 1. Do I match something, then update. 2. If I don't then insert a new document. So new means "not found" in all cases. Forget thinking about "Id Serialization", because that's just wrong and not the reason here. It's all about the "query" needing to actually find something. And it's clearly not matching when something new gets created.
    – Neil Lunn
    Nov 12 at 9:19










1




1




What about Eq("Owner", "bill") or even Eq(x => x.Owner, "bill")? Bottom line is that if it's new then it did not "match" anything. And the most likely reason here is the difference in case for the property names.
– Neil Lunn
Nov 12 at 9:00




What about Eq("Owner", "bill") or even Eq(x => x.Owner, "bill")? Bottom line is that if it's new then it did not "match" anything. And the most likely reason here is the difference in case for the property names.
– Neil Lunn
Nov 12 at 9:00












makes no difference at all.
– UberFace
Nov 12 at 9:17




makes no difference at all.
– UberFace
Nov 12 at 9:17












I want to match 2 fields, both of those are not Id, and then update all other fields (except "Id") and to create a new object if it does not exists: Upserting a object with another based on 2 fields that are not Id.
– UberFace
Nov 12 at 9:18




I want to match 2 fields, both of those are not Id, and then update all other fields (except "Id") and to create a new object if it does not exists: Upserting a object with another based on 2 fields that are not Id.
– UberFace
Nov 12 at 9:18












So show a document you expect to be updating then. As already stated the rules are pretty basic. 1. Do I match something, then update. 2. If I don't then insert a new document. So new means "not found" in all cases. Forget thinking about "Id Serialization", because that's just wrong and not the reason here. It's all about the "query" needing to actually find something. And it's clearly not matching when something new gets created.
– Neil Lunn
Nov 12 at 9:19






So show a document you expect to be updating then. As already stated the rules are pretty basic. 1. Do I match something, then update. 2. If I don't then insert a new document. So new means "not found" in all cases. Forget thinking about "Id Serialization", because that's just wrong and not the reason here. It's all about the "query" needing to actually find something. And it's clearly not matching when something new gets created.
– Neil Lunn
Nov 12 at 9:19



















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53258719%2fmongo-c-upserting-is-creating-a-new-document-instead%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53258719%2fmongo-c-upserting-is-creating-a-new-document-instead%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Florida Star v. B. J. F.

Danny Elfman

Lugert, Oklahoma