Re: Layout of "Itinerary" Record - A Database Design Question

On June 7, 2016 at 5:23 PM Nathan Andelin <nandelin@xxxxxxxxx> wrote:


We've come up with 2 alternatives for trip itinerary records and would like
to settle on one or the other:

Option 1: delineate one row for each "stop" in the route:

Surrogate_Key.
Location_ID (refers to a row in "location file").
Arrival_Date.
Arrival_Time.
Number_Of_Minutes_At_This_Stop.

Three (3) rows would be required to delineate the "steps" to a single
destination and back. Some users prefer this type of listing on screens.

Option 2: delineate one row for each "from" and "to" location in the route:

Surrogate_Key_Value.
From_Location_ID (refers to a row in "location file").
From_Location_Departure_Date.
From_Location_Departure_Time.
To_Location_ID (refers to a row in "location file").
To_Location_Arrival_Date.
To_Location_Arrival_Time.

Two (2) rows would be required to delineate the "steps" to a single
destination and back. Some users prefer this type of listing on screens.

How should we settle this debate?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.