Hi Gilles, two follow-on questions:

1.) We don't require the login or password, correct? These would need to be supplied by the client application that calls SQL Router.
2.) How do we pick the database when there are multiple choices? Should we just provide the tungsten schema, e.g., jdbc:mysql://myhost/tungsten?

Hi Robert,

To give a little background, this URL will be directly used by the SQL router to create data sources in order to offer them to the client application
1) login/pass are not required, that's ok
2) I would vote for "${DBNAME}", that would greatly simplify the router's job.
This ${DBNAME}" placeholder is the one used in the current implementation of dbname substitution in the router, so having it in the URL would allow to not touch the router code

This functionality would also be useful for
com.continuent.tungsten.replicator.ReplicatorManager.consistencyCheck(String, String, String, int, int)
method, which generates the URL by itself currently.