Hi All,
Oracle 19, Apex 24.2
I've got a decision to make; We have a requirement to capture one or more metrics for an aircraft on a regular basis. The particular metric is dependant on the specific aircraft type i.e aircraft A1 needs M1 and M4, A2 needs M1, M2, M5, M6
There are 17 metrics that are available (dare I say at this stage).
My first reaction is to create a table like;
AIRCRAFT_ID (FK to the AIRCRFAT table)
METRIC_ID (FK to the METRIC table)
METRIC_VALUE
RECORD_DATE
- Create a view to pivot the data.
- Create Instead Of Triggers on the view
- Create the data entry Form on the view
BUT the business doesnt want to see metric fields that are not applicable to the particular aircraft they are dealing with. So give each form field a Server Side condition to display if applicable to the aircraft_id
Now there are a number of other entities that use these metrics for calulcation and quite a few forms that need to display the applicable metric field(s)
My question is how bad is it to be lazy and just create a flat table versus the key-value pair?
BTW I'm leaning toward the key-value pair design
Thanks
Gary