Sounds good, thanks.

Jan


2008/6/19 Hugh Williams <hwilli...@openlinksw.com>:

> Hi Jan,
>
> In a way I was wonder if/when you might/would ask this question, as we hit
> the same issue whilst working on our Sesame/Jena/Redland RDF Providers and
> added support to the JDBC and ODBC Driver to provide this differentiation.
>
> This required updates to both the Virtuoso Server and JDBC/ODBC clients,
> thus you would need updates for both components for this to be possible. We
> are planning a new VOS 5.0.7 release either tomorrow or Monday hopefully, so
> I would suggest you wait for this release which will provide the necessary
> support you are seeking.
>
> Note that the Sesame2 RDF Provider I promised you previously should also be
> part of this release also ...
>
> Best Regards
> Hugh Williams
> Professional Services
> OpenLink Software
>
>
> On 19 Jun 2008, at 17:25, Jan Stette wrote:
>
>  Hi,
>>
>> I'm executing SPARQL queries through the OpenLink Virtuoso JDBC driver.
>>  My question is: when I look at the Java ResultSet returned after executing
>> my query, how can I get information about what type of node that each
>> variable is bound to?
>>
>> For example, if doing a simple query like:
>>
>>    sparql select distinct * where { ?subject ?predicate ?object }
>>
>> Specifically, when I get the values from column "object" in the result
>> set, string literals, URIs and blank nodes all seem to be returned as
>> Strings.  How can I distinguish between these cases?  And how can I
>> distinguish between typed and untyped string literals?
>>
>> Regards,
>> Jan
>>
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/
>> index.php_______________________________________________
>> Virtuoso-users mailing list
>> Virtuoso-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>>
>
>

Reply via email to