Hi all,
I am currently in the design phase of a project and concerned about an issue with data consistency of my database over time. I have a number of bus coaches running on a number of assigned routes. My design for the routes table, at first guess, would be something like :
Route
------
id name description date price
1 aRoute a-b-c 1/1/13 100
2 bRoute a-d-e 1/1/13 200
These routes id would then be assigned to bus coaches table to know which route they undertook. Now, suppose in the middle of the year, someone amends the Route table's description so that aRoute is now 'a-e-f' instead of 'a-b-c' and if I want to track the history of routes done by coaches, how do i do that because then the data will be corrupted if I refer to the routeID. Do I need another table to keep track of everything? Any advice on this please? Thanks
I am currently in the design phase of a project and concerned about an issue with data consistency of my database over time. I have a number of bus coaches running on a number of assigned routes. My design for the routes table, at first guess, would be something like :
Route
------
id name description date price
1 aRoute a-b-c 1/1/13 100
2 bRoute a-d-e 1/1/13 200
These routes id would then be assigned to bus coaches table to know which route they undertook. Now, suppose in the middle of the year, someone amends the Route table's description so that aRoute is now 'a-e-f' instead of 'a-b-c' and if I want to track the history of routes done by coaches, how do i do that because then the data will be corrupted if I refer to the routeID. Do I need another table to keep track of everything? Any advice on this please? Thanks