- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Tue, 12 Jul 2011 23:55:09 +0100
- To: Richard Cyganiak <richard@cyganiak.de>
- CC: public-rdb2rdf-wg@w3.org
On 7/12/11 10:07 PM, Richard Cyganiak wrote: > On 12 Jul 2011, at 21:12, Kingsley Idehen wrote: >> On 7/12/11 8:25 PM, Richard Cyganiak wrote: >>> I'd add: >>> >>> - authenticating user password >>> - JDBC driver class name >>> - JDBC connection properties >>> - the base IRI >>> >>> This would complete the list of things one can specify in D2RQ (all optional). A couple of them are wrapped into a JDBC URL. >> What about ODBC ? > We didn't support it in D2RQ (except for what you can do with JDBC-ODBC bridges) since we were in a Java environment. > > For R2RML neither JDBC nor ODBC are really all that great because both of them are tied so strongly to a particular implementation environment. > > But defining a new, third option is of course also bad. What I am trying to highlight is the fact that SQL connections can be abstracted by merging JDBC and ODBC connections strings. They are both from the SAG CLI genealogy. There's little between them. Every RDBMS is ODBC and JDBC accessible, so we can list all the Attribute=Value pairs that constitute a connection URL. > Hence my proposal to POSTPONE. If need be, Ted can pick up and deliver it quickly. Kingsley > Best, > Richard > > >> Links: >> >> 1. http://www.connectionstrings.com/ >> 2. http://wiki.lazarus.freepascal.org/ODBCConn#The_ODBC_connection_string . >> >> -- >> >> Regards, >> >> Kingsley Idehen >> President& CEO >> OpenLink Software >> Web: http://www.openlinksw.com >> Weblog: http://www.openlinksw.com/blog/~kidehen >> Twitter/Identi.ca: kidehen >> >> >> >> >> >> > -- Regards, Kingsley Idehen President& CEO OpenLink Software Web: http://www.openlinksw.com Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca: kidehen
Received on Tuesday, 12 July 2011 22:55:40 UTC