Finished coding and testing SQLiteReservationsDAO

Well actually you're right. A reservation belongs to a user. But it looks like you're adding seat quantity to it, and that seems like it shouldn't belong to a reservation, rather a flight. That's what was throwing me off lol. So we could either ditch that, or simply make a flight class that we can pass around. So if we're using seat quantity lets create a flight class