Home/ Questions/Q 1055273
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T17:32:14+00:00

i have an event calendar application with a sql database behind it and right

  • 0

i have an event calendar application with a sql database behind it and right now i have 3 tables to represent the events:

Table 1: Holiday
Columns: ID, Date, Name, Location, CalendarID

Table 2: Vacation
Columns: Id, Date, Name, PersonId, WorkflowStatus

Table 3: Event
Columns: Id, Date, Name, CalendarID

So i have “generic events” which go into the event tableand special events like holidays and vacation that go into these separate tables. I am debating consolidating these into a single table and just having columns like location and personid blank for the generic events.

Table 1: Event:
Columns : Id, Date, Name, Location, PersonId, WorkflowStatus

does anyone see any strong positives or negative to each option. Obviously there will be records that have columns that dont necessarily apply but it there is overlap with these three tables.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Either way you construct it, the application will have to cope with variant types. In such a situation I recommend that you use a single representation in the DBM because the alternative is to require a multiplicity of queries.

    So it becomes a question of where you stick the complexity and even in a huge organization, it’s really hard to generate enough events to worry about DBMS optimization. Application code is more flexible than hardwired schemata. This is a matter of preference.

    • 0