Currently, I am exploring the most effective approach for my Ember App.
I am dealing with two separate models: events and bookings. In my database, I have structured them in a completely independent manner.
Schemas:
Events:
attributes:
date : Date
description : String
hiw : Object
hour : Date
meeting : String
men : Number
name : String
women : Number
createdAt : Date
updatedAt : Date
isActive :
type : Boolean
default : false
type:
type : String
default : 'event'
Bookings:
attributes:
email : String
idiom : String
name : String
obs : String
participants : Number
phone : String
sex : String
vip : String
createdAt : Date
updatedAt : Date
isActive :
type : Boolean
default : false
type:
type : String
default : 'booking'
While learning Ember, I have come to understand that Ember offers relationships such as belongsTo and hasMany. I am unsure whether I should restructure my schemas to align with Ember or continue with my current independent setup.
The complexity of bookings is expected to increase over time.
Are Ember relationships designed for managing such intricate data structures or are they more suited for simpler tasks like handling comments on posts?
Thank you!