You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some of the parameters of vroomX functions are optional, hence the signatures need to change to have the optionals as last named parameters, just like we do it on pgRouting.
This signature change can be done as part of 0.5.0
For all the vroom functions:
Breaks SQL is optional.
All the time windows are optional, if present (Jobs Time Windows SQL, Shipments Time Windows SQL, Breaks Time Windows SQL).
For vrp_vroom and vrp_vroomPlain:
Either of Jobs SQL or Shipments SQL can be NULL, but both Jobs SQL and Shipments SQL cannot be NULL.
@cvvergara We can maybe make both Jobs SQL and Shipments SQL required for this function - what do you say? We have other functions where Jobs SQL is not present (vrp_vroomShipments, vrp_vroomShipmentsPlain) or Shipments SQL is not present (vrp_vroomJobs, vrp_vroomJobsPlain).
Vehicles SQL and Matrix SQL are always required.
The text was updated successfully, but these errors were encountered:
Ref: Topic on Discourse https://discourse.osgeo.org/t/confused-with-vroom-functions-on-vrprouting/50928/1
Some of the parameters of vroomX functions are optional, hence the signatures need to change to have the optionals as last named parameters, just like we do it on pgRouting.
This signature change can be done as part of 0.5.0
For all the vroom functions:
Breaks SQL
is optional.Jobs Time Windows SQL
,Shipments Time Windows SQL
,Breaks Time Windows SQL
).For vrp_vroom and vrp_vroomPlain:
Jobs SQL
orShipments SQL
can be NULL, but both Jobs SQL and Shipments SQL cannot be NULL.Jobs SQL
andShipments SQL
required for this function - what do you say? We have other functions where Jobs SQL is not present (vrp_vroomShipments
,vrp_vroomShipmentsPlain
) or Shipments SQL is not present (vrp_vroomJobs
,vrp_vroomJobsPlain
).Vehicles SQL
andMatrix SQL
are always required.The text was updated successfully, but these errors were encountered: