× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. June 2016

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


Interesting question. It would help to know some more about the usage case.


The use case is to schedule itineraries for bus trips, to assign drivers
and buses to trips, to calculate or derive miles and minutes between legs,
to calculate the cost of trips, and such.

Option 1 would need some kind of sequence to indicate what order the stops
are visited in if there is more than one stop on the journey/route, though
conceivably you could use the arrival time for the same purpose.


We were thinking of using the surrogate key to sequence stops under option
#1.

I favour option 2 in that is seems to me it would better support a journey
other than a single return journey. Calculating durations would also be
simpler than messing with arrival times in separate records.


Thanks for your point of view.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.