ISSUE-65: For uniformity and performance, "literal" triples must be always generated for each child table column in a foreign key

ISSUE-65: For uniformity and performance, "literal" triples must be always generated for each child table column in a foreign key

http://www.w3.org/2001/sw/rdb2rdf/track/issues/65

Raised by: Souripriya Das
On product: 

The following portion within double quotes is from email [1]:

"
In section 2.1 we are NOT generating a literal triple for the column addr. So, we are only generating:
<People/ID=7> <People#addr> <Addresses/ID=18> .

I would propose that we generate two triples: one literal triple and one IRI triple:
<People/ID=7> <People#addr> "18"^^xsd:integer .
<People/ID=7> <People,Addresses#addr,Id> <Addresses/ID=18> .
"

Currently we are not generating literal columns for column included in a single-column foreign key. This introduces non-uniformity with multi-col foreign key case and introduces need for unnecessary join with the parent table to retrieve the value of the foreign key column.

[1] http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2011Aug/0055.html

Received on Tuesday, 9 August 2011 16:47:19 UTC