Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> comp.databases.theory -> re:Data modeling issues for a travel planning system

re:Data modeling issues for a travel planning system

From: kevin <kevin.pang_at_gmail-dot-com.no-spam.invalid>
Date: Sat, 05 Nov 2005 02:10:29 -0600
Message-ID: <s6idnTMAUJ9o9fHeRVn_vA@giganews.com>


In STATION_LINE table, although three fields make one unique record, I still prefer using an unique ID as the primary key, and control the logic in the program.

The definitions are not very reasonable IMHO, direction_id should be placed in the line and doesn't have to be repeated in every record of STATION_LINE. It's better not to use nextstat_id if there are not many stations in one line, it would be very inconvenient to navigate.

How about this:

LINE:
- (PK) ID (integer)

STATION_LINE:
- (PK) ID (integer)

For example: to list all stations of a line in order: select id from STATION_LINE order by order_number. Received on Sat Nov 05 2005 - 02:10:29 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US