Brandon

My feedback

  1. 67 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Storage » Blobs  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon supported this idea  · 
  2. 526 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  API Management » Security  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon supported this idea  · 
  3. 1,035 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    26 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon supported this idea  · 
  4. 1,067 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  17 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon supported this idea  · 
  5. 416 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon supported this idea  · 
  6. 502 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Azure Cosmos DB » SQL API  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your feedback. I have discussed this in more detail with our team.

    You are correct the workaround suggested to use .AsEnumerable().FirstOrDefault(). should not be a recommended work around. This way results in materializing all documents on the client first before getting the 1st document, which is not very efficient and the exact opposite of what you are trying to achieve.

    Instead we recommend you use Take(1).AsEnumerable() and then .First() or .Single() or .FirstOrDefault() for Single() and First(). Take(1) is translated to SELECT TOP 1 and is processed server-side so more efficient than the previous suggestion and is what you are trying to achieve.

    As to the original ask. The support for these operations can be done, but this work is not prioritized against the other work we want to deliver. I will move this back as unplanned but please note this is on our roadmap.

    Thanks again…

    An error occurred while saving the comment
    Brandon commented  · 

    I ran into this too. A reasonable (though annoying) workaround is

    .Where(x => x.Id == id).AsEnumerable().SingleOrDefault()

    and this can be rewrapped as an extension method

  7. 4,860 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    117 comments  ·  Azure Cosmos DB » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon supported this idea  · 
  8. 713 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  115 comments  ·  Azure portal » Search + navigation  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon supported this idea  · 

Feedback and Knowledge Base