Re: DB URL syntax with table level specificity?

in message <1113592318.411097.249340@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
Robert ('robert.beltran@xxxxxxxxx') wrote:

> Generally, you really shouldn't be doing anything dynamic with the
> URL.
> You use it to setup the connection manager and that is it. Are you
> working with an app server? You can make schemas and table spaces,
> and permissions if you want to limit the access of a certain user.

Yup, but at the level of data abstraction I'm dealing with it shouldn't
much matter whether the data source is a mail file, an SQL database, an
LDAP directory, a web service, or whatever. I need a means of
addressing each through the same abstract interface - all the actual
sorting out how to talk to the data needs to be hidden. Essentially at
the application layer it shouldn't matter where or how the data is
actually held (and the application layer programmer shouldn't have to
know).

I can talk to each of the other data sources I'm looking at with a
unique RFC 1738 syntax URL without too much bending of things. However
a relational database is not so much a data source as a data source of
data sources, and I need to be able to address it at table level.

If I can construct a URL schema which will encapsulate all existing JDBC
schemas and allow me to extract the original URL and the additional
tokens I need with a simple RFC 1738 parser life will be very simple.
What I'm wondering is where the nasty little gotchas which will wake up
and bite me six months down the line will come from.

I agree that application layer programmers shouldn't do what I'm doing,
but unless someone does what I'm doing you don't get things like JDBC
in the first place.

--
simon@xxxxxxxxxxxxxx (Simon Brooke) http://www.jasmine.org.uk/~simon/
Das Internet is nicht fuer gefingerclicken und giffengrabben... Ist
nicht fuer gewerken bei das dumpkopfen. Das mausklicken sichtseeren
keepen das bandwit-spewin hans in das pockets muss; relaxen und
watchen das cursorblinken. -- quoted from the jargon file

.