You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is true, and unfortunately this would require a bit of a redesign of the API, since all methods that target a document by id only accept strings as ids:
I suppose this could be rewritten, but it won't happen in the next couple of days.
Thanks for you reply. I fully understand this is a huge change.
However, the string id shouldn't be an issue as I'm using a Guid converted to a string in my documents.
example:
Oh, I see. Then I suspect it's the StringObjectIdConvention that might be the problem. I think there's an argument for why that shouldn't even be a part of this library in the first place. I might be able to remove it.
I'm facing an issue when the primary key is other than ObjectId.
We're using
Guid
strings asId
field.When using
ReplaceOneAsync
I'm getting the error message"'760a812e-7bd1-42f2-9892-75486e809655' is not a valid 24 digit hex string."
it's working correctly with the plain Mongo C# driver.
The text was updated successfully, but these errors were encountered: