Topic: One model or two?
I'm torn as to whether to store flight details for my app in one model or two. Basically - Departures and Arrivals have the same fields:
flight_number from_airport to_airport departure_date departure_time arrival_date arrival_time etc.
For my current purpose though, I'm only interested in arrival date/time for inbound flights, and departure date/time for outbound flights. So should I combine departures and arrivals into one table, and use just one date/time columns for both departure & arrival times, with a flag for whether the flight is an arrival or departure? Or am I better off keeping them separate?
The controllers / views will probably have some logic / presentation in common, bu t not all - at the very least will have to refer to arrivals or departures depending on flight direction, but may also follow a different logic in places, so combining may complicate things in places.
Advice / suggestions appreciated!
PS. Separate Date / Time columns, or one DateTime column?