Getting a single object from mongodb in C#
Asked Answered
B

4

13

I've picked up a piece of code that is using the MongoDB driver like this to get a single object from a collection...this can't be right, can it? Is there a better way of getting this?

IMongoCollection<ApplicationUser> userCollection;
....
userCollection.FindAsync(x => x.Id == inputId).Result.ToListAsync().Result.Single();
Belting answered 1/7, 2015 at 20:52 Comment(0)
C
31

Yes, there is.

First of all don't use FindAsync, use Find instead. On the IFindFluent result use the SingleAsync extension method and await the returned task inside an async method:

async Task MainAsync()
{
    IMongoCollection<ApplicationUser> userCollection = ...;

    var applicationUser = await userCollection.Find(_ => _.Id == inputId).SingleAsync();
}

The new driver uses async-await exclusively. Don't block on it by using Task.Result.

Carmelcarmela answered 1/7, 2015 at 21:25 Comment(3)
Also, rather than having to catch the InvalidOperationException on a miss consider FirstOrDefaultAsync() instead of SingleAsync()Fascia
@Fascia Single enforces there's only a single matching item and no more. Using First can hide data errors. If you want to support a case when there's not even a single matching item you can use SingleOrDefaultAsyncCarmelcarmela
I'm using the latest driver. Should we do Find+SingleAsync, or FindAsync+SingleAsync, or is it the same thing in the end?Drucilladrucy
B
8

You should limit your query before executing, otherwise you will first find all results and then only read one of it.

You could either specify the limit using FindOptions in FindAsync, or use the fluent syntax to limit the query before executing it:

var results = await userCollection.Find(x => x.Id == inputId).Limit(1).ToListAsync();
ApplicationUser singleResult = results.FirstOrDefault();

The result from ToListAsync will be a list but since you limited the number of results to 1, that list will only have a single result which you can access using Linq.

Bannockburn answered 1/7, 2015 at 21:5 Comment(5)
Why do you use limit in query with condition by primary key? Why do you use ToListAsync and then FirstOrDefault? I don't understand who could upvote this answer.Masbate
@Masbate (1) Id is not guaranteed to be a primary key I think. (2) I was not aware of the existence of IFindFluentExtensions, as such I couldn’t know about SingleAsync. (3) The implementation behind SingleAsync does use a limit too. (4) ToListAsync is one way to execute an IFindFluent query and simpler to use than the cursor. (5) ToListAsync still returns a list, so if you want to get the actual item, you need to access that first, e.g. using FirstOrDefault.Bannockburn
@Masbate I know about _id but after reading through the documentation I found no proof yet that this is always mapped to the Id property in .NET. Instead, I have something that suggests that this does not always need to be the case.Bannockburn
Id Mapping documentation: mongodb.github.io/mongo-csharp-driver/2.0/reference/bson/…Narthex
Note that .Find(...).FirstOrDefault() is already provided, and it does a .Limit(1) under the covers: github.com/mongodb/mongo-csharp-driver/blob/…Antemeridian
R
2

In newer versions of MongoDB Find() is deprecated, so you can either use

collection.FindSync(o => o.Id == myId).Single()

or

collection.FindAsync(o => o.Id == myId).Result.Single()

You can also use SingleOrDefault(), which returns null if no match was found instead of throwing an exception.

Rathe answered 20/4, 2021 at 18:10 Comment(1)
Thanks for you answer!!Hoatzin
D
0

I could not get the method:

coll.Find(_ => _.Id == inputId).SingleAsync();

To work as I was getting the error

InvalidOperationException: Sequence contains more than one element c#

So I ended up using .FirstOrDefault()

Example:

public FooClass GetFirstFooDocument(string templatename)
        {
            var coll = db.GetCollection<FooClass>("foo");
            FooClass foo = coll.Find(_ => _.TemplateName == templatename).FirstOrDefault();
            return foo; 
        }
Document answered 28/7, 2017 at 18:49 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.