Jamie Gaskins

Sorry for the delayed response. It's been a hectic week. :-) For relationships between objects, here's what you can do currently (I use the concept of an article because it...

If the queries went from this: ``` ruby mapper.select { |foo| (foo.name == 'bar') & (foo.baz == 'quux') } ``` to this: ``` ruby [[:name, :==, 'bar'], :and, [:base, :==,...

It looks like I need to add this to the README, but you'll want to add [this line](https://github.com/ewamarciniak/DM_app/blob/05aa422cd9d1d051e95c0185794a110043dc78dc/config/environments/development.rb#L38) to `config/initializers/perpetuity.rb`. I noticed you had it in several places in your...

If no indexes are being added, that's definitely a bug. The idea behind `reindex!` is that, after it's run, the indexes in the table should be exactly as you have...

I had a look at your `Document` mapper. It looks like the index isn't being created because it's trying to index the `project` attribute, which is stored in a `JSON`...

I am, but it'll require quite a bit of work with the query parser. For example, given the following mappers: ``` ruby Perpetuity.generate_mapper_for Article do # ... attribute :author, type:...

Yep. It'd be pretty nice to have other options to store/retrieve attributes. I like the ivars as the default (since I'd bet that's the most common). I originally thought about...

Hmm … It seems some of the things I mentioned here might conflict with what we've discussed in #15. Maybe using procs might not be a good idea and we...

Not yet. I would absolutely love to have it, it was part of the plan from the beginning, but it requires knowledge of two things that I haven't determined how...

Funny you mention `dry-struct`, solnic (not @-mentioning him so I don't opt him into this thread) told me a while back that this is kinda what `dry-struct` does, but it...