topic closed

First of all your table schema is really kinda complicated.But some of your tables should have one item in common that way when they call one the one being called calls the other.E.g like your city when referencing city by flight name it will pull up flight then something else in common and so on.You know what am at wedding right now.I'll get home and digest this.But this table design is really professional.Bye

First of all your table schema is really kinda complicated.But some of your tables should have one item in common that way when they call one the one being called calls the other.E.g like your city when referencing city by flight name it will pull up flight then something else in common and so on.You know what am at wedding right now.I'll get home and digest this.But this table design is really professional.Bye

so wat are suggesting i do, cos this is what am working with now but if u feel i need to make changes do that and show it to me , will really appreciate a quick response today its quiet urgent, thanks

amm still waiting pls

Hello

Price should be in its own table, since it can change and you might have different prices for the same flight.
Is the relationship between schedule and reservation correct, a schedule should have several reservations(not the other way round)

A customer also has several reservations (reservation details should not be in customer)


Gotta go, i'll look at it later (Your relationshiop seem upside down though ),

Cheers

any luck yet

It'll be easier if you describe the business process you're trying to model.
The answer to your question depends on the details of the problem you're working on.