'n' number of possible itinerary items

[NathanielB]

If I need to build a list of itineraries within a database, but I am unsure as to the amount of actual itinerary items within the list, how do I go amonst building a table?

i.e., lets say for one itinerary there is seven stops, but another itinerary has eleven stops. They're all in the same table.

What would a database achitecture look like for a dynamic amount of stops per each itinerary?

[r937]

What would a database achitecture look like for a dynamic amount of stops per each itinerary?

there would be one table for itineraries, and another table for stops, such that the itinerary of each stop is a foreign key in the stops table

the 'n' number of possible items would be handled by a variable number of stop rows per itinerary

[NathanielB]

Hi r937, thanks for the quick response!

What would happen if I needed to relate one itinerary (which has a group of stops) to a specific trip code, which is in a trip_details table?

[IBazz]

Is the trip code unqiue to each itinerary? if so, you code add it as a column in the itinerary table.

if the trip code relates to more than one itinerary, I would consider treating it in the saem way as r937 suggested you treat 'stops'.

I am getting a hint that your db may not be fully normalised yet. it might help if you were to post your table structure in case we can help further.

bazz

[NathanielB]

Is the trip code unqiue to each itinerary? if so, you code add it as a column in the itinerary table.

if the trip code relates to more than one itinerary, I would consider treating it in the saem way as r937 suggested you treat 'stops'.

I am getting a hint that your db may not be fully normalised yet. it might help if you were to post your table structure in case we can help further.

bazz

Hi guys, sorry Christmas has been taking time away from me.
The trip codes will be unique for each itinerary; I'll get a EER Diagram up by tomorrow