Sha256: 3840937e0152ea17895d80d934fa3c92d3068c9d34b0e897f4013111acba7985
Contents?: true
Size: 1.16 KB
Versions: 4
Compression:
Stored size: 1.16 KB
Contents
(channel spec) (stream spec) Stream -> [parent] Channel -> [from parent model] [intermed] Feed -> [intermediary relation] [from nested...] (*) Blog -> [ from nested assn...? ] Post we need a process that starts the other way, and 'completes' the through like a belongs_to :through ... ? for stream spec: - nested assn is (channel has_many posts through feeds) if we could get at (feed has_many posts through blogs) i think we could recurse? note: it should be the 'nested assn' for (channels has_many posts)... - intermediray relation is (stream has many channels...) # through can we get at channels has many posts? in this context Channel is `intermediary_relation.child_class_name.to_s.singularize.constantize' [ ugh! ] Post.where(blog_id: 1) Post.where(blog: { feed_id: 234 }) Post.where(blog: { feed: { channel_id: 567 }}) Post.where(blog: { feed: { channel: { stream: 890 }}}) # network.posts.recent Post.where(published_at: 1.day.ago...Time.now, blog: { feed: { channel: { stream: { network_id: 1234 }}}})
Version data entries
4 entries across 4 versions & 1 rubygems
Version | Path |
---|---|
passive_record-0.4.11 | notes.md |
passive_record-0.4.10 | notes.md |
passive_record-0.4.8 | notes.md |
passive_record-0.4.7 | notes.md |