|
Duvida
|
June 10, 2014 at 8:44 am
You could provide me with the data model and a logic behind it?
wp_events_answer
wp_events_attendee
wp_events_attendee_meta
wp_events_category_detail
wp_events_category_rel
wp_events_detail
wp_events_discount_codes
wp_events_discount_rel
wp_events_email
wp_events_locale
wp_events_locale_rel
wp_events_meta
wp_events_multi_event_registration_id_group
wp_events_personnel
wp_events_personnel_rel
wp_events_prices
wp_events_qst_group
wp_events_qst_group_rel
wp_events_question
wp_events_start_end
wp_events_venue
wp_events_venue_rel
MailChimp Integration
———————————
wp_events_mailchimp_attendee_rel
wp_events_mailchimp_event_rel
Member integration
———————————
wp_events_member_rel
Recurring
———————————
wp_events_recurrence
Ticketing
———————————
wp_events_ticket_templates
wp_events_attendee_checkin
|
|
Sidney Harrell
|
June 11, 2014 at 11:11 am
We do not have a database diagram for EE3. It is fairly straightforward, though. The “rel” tables allow a many-to-many relationship, such as between events and venues. Anywhere you find the ID of one table used as a key in another table, it allows for a one-to-many relationship. For example, the ID of the attendee table is used as a key, attendee_id, in the answers table.
|
