Returning multiple ids with Load()

[Starfish]

I'm having trouble loading a bunch of documents that with known ids with a load operation.

Code is:

var savedThreads = session.Load<Thread>(requestBody.SavedIds);

Maps to:

http://localhost:8121/queries/?&id=669410&id=669409

Gives HTTP 200:

{

• Results: [ ],
• Includes: [ ]

}

But I have these documents! Raven build 2142.

[Starfish]

OK, I forgot the collection before id. Sorry everyone! :(

[Felipe Leusin]

I've made this mistake several times in the past. Never found an elegant way of doing it so I just wrote an extension method:

public static T[] Load<T>(this IDocumentSession session, ValueType[] ids)

        {

            var typeTagName = session.Advanced.DocumentStore.Conventions.GetTypeTagName(typeof (T));

            return session.Load<T>(ids.Select(x => string.Format("{0}/{1}", typeTagName, x)));

        }

I think it's something like this, just wrote this out of memory.

[Chris Marisic]

This is a rather naive method.

Taking the most advantage of raven as you can you will end up with documentIds like foo/1/bar/2/baz/3, even without rich document ids like that you really don't want to be dealing with id: "123" and trying to infer that to "contacts/123" you want to have "contacts/123" on hand.

[Felipe Leusin]

Just because it's naive doesn't mean it's not usefull on some situations.

I used it on a application where the Ids where the facebook profile Id (I needed a fast way to check if a user had been registered on RavenDb either by himself or as a friend of someone) and it was helpfull.

[Chris Marisic]

The issue with this is using methods like this as a standard practice you're going to fixate on id is 123, not that id really is "contacts/123" and that's a very bad choice in RavenDB IMO.

[Chris Marisic]

 Its fine if you're doing things like convert a sequence of facebook userIds to user/{facebookId} but outside of that scenario I'd say it's a value negative.