On Wed, Sep 9, 2009 at 3:31 AM, John Andersen <[email protected]> wrote: > > Are the non-members information important after the meeting? Are there > non-members, who participates repeatedly? > Must non-members provide information on themselves every time, or can > they use their previous non-member information? > > What are the current use of the members? Does the non-members conflict > with that usage?
All very good questions. I've already asked a couple of them but no clear response from the client. I thought that I'd add a lookup for non-members' previous info on subsequent registrations. Something like, "enter your email address if you've registered for previous meetings". I don't think there are any security implications as the person still has to pay and we're not storing any payment info. So someone couldn't just use someone else's credit card at random. The thing that really bugs me about storing both members and non-members in the same table, though, is that the latter will keep accumulating because we might end up with a lot of non-returns, year after year. > My suggestion is (until the above is clarified): > > one meeting -> has many -> attendees -> which may be -> a member or a > non-member > > In CakePHP terms: > meetings -> attendees <- members > meetings -> attendees <- non-members This is closer to what I sort of had in mind. But I can't quite figure out how I'd do a find(), or how to set up the Attendee model, for that matter. I've just got vague notions right now. Could you elaborate? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
