Database schema for calendar application -
i'm creating calendar application in each date has 1 of 3 states: available, maybe available, , unavailable. trying figure out best schema situation.
one thought might have userdate model field state
. problem db have #-of-users- x 365
rows each year - seems grow modestly sized app.
another thought might have default state, , create userdate object when user has signified availability on date different default. seems convoluted though.
has dealt situation before? suggestions on best way go this?
when create new user, not want inserting records next 50 years of life. creating userdate object when there non-default value should do.
you consider storing range of dates user if have lots of consecutive dates same status. example, if unavailable of december, represented single row.
think sort of information want extract database, , how difficult each of possible designs.
Comments
Post a Comment