mysql - Accommodating waypoints in a SQL table -


I am currently making a table to store taxi bookings.

Enter image details here

Key < ID - Booking ID

Customer ID - What is being raised

Driver ID - ID selected for customers

P>

Pickup Aid - Pickup Location

Pickup Wave - Latitude Coordination of Pickup Space

Loan Coordination of Pickup Transaction Pickup Locations

DropoffEders Skip

Dropoff Wave - Latitude Coordination of Dropoff Location

Poor loan - Coordination of loan dropoff location

Mileage - Distance between pickup edder and dropoffender, with any other stops made

Stop - Number of routes / stops during travel

Price - What is the payment this customer has to pay for this part in the journey

I am facing the problem moment it is not that I do not know How to deal with way points.

For example, if you have been raised on A to B, but decided to stop A1 and A2 during the trip to take some friends (all booked beforehand Was)

What would be the best way to reconstruct my current table, adjust it?

Should it come in the form of a separate line or column? As this data is dynamic (i.e. a number of pickup / dropoffs can not be expected during a visit by a customer), what should I do?

Since this is one-to-many relationship, it should be a separate table:

  • id - Waypoint id
  • booking_id - bookings by fire table
  • Sequence - Order within such a point
  • edit - pathpoint address
  • latitude Longitude
  • long - longitude of path point

If you wish, you can pickup XXX And DropoffXXX column to the table, and simply use the Wrenchpoint table for this, the pickup may be the first point-point, and the dropoff will be the last.


Comments

Popular posts from this blog

java - org.apache.http.ProtocolException: Target host is not specified -

java - Gradle dependencies: compile project by relative path -

ruby on rails - Object doesn't support #inspect when used with .include -