- From: Robert Scanlon <rscanlon@revelytix.com>
- Date: Fri, 11 Feb 2011 08:58:56 -0600
- To: David McNeil <dmcneil@revelytix.com>, Souripriya Das <SOURIPRIYA.DAS@oracle.com>
- Cc: public-rdb2rdf-wg@w3.org
Received on Friday, 11 February 2011 18:06:35 UTC
I agree with David, this property should be optional. I would like to see the tableOwner removed from *most* test cases (except property-focused tests specifically meant to test that property). That provides more flexibility to test implementers to automate the tests, without having to create a *single* special schema. (It also allows for test implementers to create a unique schema per testcase if they want, or to try the test cases on different schemas that have different characteristics). Bob On Fri, Feb 11, 2011 at 7:54 AM, David McNeil <dmcneil@revelytix.com> wrote: > Souri- > > I think the tableOwner property should be optional. Using tableOwner and > tableName is a short-hand for the SQLQuery: > > SELECT * FROM <tableOwner>.<tableName> > > When writing this query by hand the tableOwner is optional. In the same way > I think tableOwner should be optional when using the tableName property. > This allows the author of the SQL to either use the tableOwner if it is > needed in their context or to omit it if it is not needed. In my experience > it is common to write SQL queries with unqualified table names and rely on > the user to only be specified as part of the connection properties. > > -David >
Received on Friday, 11 February 2011 18:06:35 UTC