16:35 <jammanbo> Can a has n cross repositories?

16:36 <jammanbo> User is in one repo, Session in another, User has n, :sessions. I can read a Session and a User directly just fine, but it gets confused when I ask it for @user.sessions.

16:37 <jammanbo> looks in wrong repo; chokes on properties.

16:37 <jammanbo> makes me feel very violent

16:38 <onewheelskyward> You've set your storage names?

16:38 <onewheelskyward> I'm pretty sure I'm doing this

16:39 <jammanbo> @!&**$

16:40 <jammanbo> WTF is that option not documented

16:40 <onewheelskyward> Yep I'm doing it, and it works fine.

16:40 <jammanbo> I wasn't setting the repository on the association

16:40 <jammanbo> Have it working now.

16:40 <onewheelskyward> On the association? That's neat. I use this: def self.default_repository_name

16:40 <onewheelskyward> in my model.

16:41 <onewheelskyward> Otherwise it assumes everything is in your default repo.

16:41 <jammanbo> Yeah, that's what I'd tried. That makes it possible to do User.first and Session.first and hit the right repos. But when I did @a_user.sessions, it was trying to load Sessions from the User repo

16:41 <onewheelskyward> oh weird

16:42 <onewheelskyward> I probably don't use that way of finding.

16:42 <jammanbo> Have to manually tell it where to find sessions, i.e. this in user.rb

16:42 <jammanbo> has n, :sessions, repository: :default

16:43 <jammanbo> DM may yet kill me :/

16:54 <onewheelskyward> okbai!