RE: [Sparql4j-devel] M1 reached?

[Seaborne, A. <and...@hp...>]

-------- Original Message --------
> From: Samppa Saarela <mailto:sam...@pr...>
> Date: 13 January 2006 15:18
>=20
> > > So you suggest allowing $'s also as parameter slots? I guess/hope
> > > that adding support for this is trivial...
> > >=20
> > >=20
> >=20
> > The reverse is what I had in mind.  Writing the query with $subject.
> >=20
> >=20
>=20
> It might cause confusion about what is parameter slot and what is
> variable - even I'm not quite sure if you mean a parameter slot or
> variable by that $subject? =20


select * where {$subject rdfs:label ?;=20
                         rdfs:comment $comment .=20
                filter ($comment < ?) .}


>=20
> The format for parameter slots should be distinct from variables,
> otherwise e.g. variables used in a select-clause might get confuced as
> parameter slots and become replaced... =20
>=20
> > Named paramters are much better than pure postional!
> >=20
> >=20
> Absolutely! ...but there's no support for name parameters in JDBC
which
> is our primary objective. If named parameters are used, the format
used
> for *should* be distinct from variables (got better ideas than
> ?{paramName} syntax?) because JDBC offers primarily (i.e. only)
> positional parameters. However, we have been discussing (with Timo)
> about JDBC extension allowing one to bind parameter slots into
> variables, e.g.     =20
>=20
> select * where {? foo:predicate ?object}
>=20
> stmt.setVariable(1, "subject");
>=20
> --> select * where {?subject foo:predicate ?object}
>=20
>=20
> Have a nice weekend!
>=20
> Br,
>   Samppa