Colin Law wrote in post #1166568:
> On 12 January 2015 at 21:40, David Williams <lists@ruby-forum.com>
> wrote:
>> Right now,
>> my Event.rb
>> has belongs_to :activism_co_user
>
> What??
>
>> has_one :category
>>
>> Activism_co_user.rb
>> has_many :events
>>
>> The table itself has quite a few properties that describe what the event
>> will be and how many people can attend. What I would I like to is allow
>> them to limit the amount of tickets for an event, and let users pick
>> options like donate to their charity using a stripe mechanism during
>> checkout
>
> If I understand correctly then possibly you will want a join model
> called something like attendance where
> user has_many attendances
> user has_many events through attendances
>
> event has_many attendances
> event has_many users through attendances
>
> attendance belongs to event and belongs to user.
>
> What on earth is an activism_co_user?
>
> Colin
I apologize, that would be the name of the second user model. From what
you're telling me. I need another model named attendances. What might
the contents of that model pertain? I'll refractor the name of the
second user model before going into production. (I won't let normal
users create their own events btw.) The create action will only be
available on the company's side to avoid criminal activities.
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/3576aea8b91a5422fc86bb37ad65c1eb%40ruby-forum.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment