On Tue, Jul 24, 2012 at 12:52 PM, Tim Shadel <timsha...@gmail.com> wrote:
> Cool. So for some like "Facebook," you're mostly starting from one very
> well known id (the user that logs in), and then finding data through
> relationships as they move around the app. That's the scenario that fits
> ToyStore pretty well, and that makes sense since a huge swath of apps are
> actually a lot like that. Thanks!

> Any libs or specific query patterns you recommend for scenarios you hit
> here and there?

> --Tim

> On Jul 24, 2012, at 9:29 AM, John Nunemaker <nunema...@gmail.com> wrote:

> Correct. What I often do is add in other query patterns I need as I need
> them. ToyStore could work with regular sql type data stores probably, but
> I've never tried it. It is more geared for querying by a single key.

> If you need more than a single key, you are on your own. The great thing
> is that with most nosql-ish data stores, adding a few queries on top of
> toystore is very easy.

> On Tue, Jul 24, 2012 at 10:19 AM, Tim Shadel <timsha...@gmail.com> wrote:

>> If I've read the docs correctly, there isn't anything in there about
>> finding an object by anything but id. Is that right?  ActiveRecord methods
>> like Model.all are the kind that _didn't_ move to ActiveModel, if I
>> followed the split.  So I'm assuming that _finding_ objects (by query or by
>> 'all') is a different concern than loading, setting, saving, and managing
>> the relationships on those objects. So ToyStore is awesome, and I should
>> get an Adapter-specific way of searching for records. Is that the approach
>> to take?

>> Thanks!

>> Tim