Mulgara Project: Issueshttps://code.mulgara.org/https://code.mulgara.org/favicon.ico?15861924492012-02-07T21:37:21ZMulgara Project
Redmine Mulgara - Bug #213 (New): Error on ORDER BY variables projected away by SELECT clausehttps://code.mulgara.org/issues/2132012-02-07T21:37:21ZAlex Hall -alexhall@revelytix.com
<p>A SPARQL query that mentions a variable in an ORDER BY expression that appears in the WHERE clause but is projected away by the SELECT clause incorrectly causes an exception to be thrown. According to SPARQL, ordering is applied prior to projection, so this should be valid. This appears to be a case where TQL and SPARQL semantics are mis-aligned.</p> Mulgara - Bug #136 (New): IntervalConstraintDescriptor converts all bounds to xsd:doublehttps://code.mulgara.org/issues/1362008-08-04T20:04:13ZAlex Hall -alexhall@revelytix.com
<p>The <code>Bounds</code> object used by <code>IntervalConstraintDescriptor</code> to store the upper and lower bounds of a constraint stores the bounds as doubles. The <code>IntervalConstraintDescriptor.resolve(...)</code> method always uses <code>SPDouble</code> objects constructed from these bounds when slicing the stringpool. This makes it impossible to compare on datatypes derived from <code>xsd:decimal</code> (i.e. <code>xsd:int</code>, <code>xsd:long</code>, etc).</p>
<p>For instance, the following sequence of TQL commands produces no results:</p>
<pre>
create <rmi://localhost/server1#test>;
insert <test:foo> <rdf:value> '1'^^<http://www.w3.org/2001/XMLSchema#int>
into <rmi://localhost/server1#test>;
select $x from <rmi://localhost/server1#test> where
$x <mulgara:gt> '0'^^<http://www.w3.org/2001/XMLSchema#int> in <sys:xsd>;
</pre> Mulgara - Bug #135 (New): Mulgara keeps file lock if parsing of RDF/XML failshttps://code.mulgara.org/issues/1352008-07-29T20:48:41ZAlex Hall -alexhall@revelytix.com
<p>Running Mulgara 2.0.0 on Windows XP, if the parsing of an RDF/XML file fails due to illegal content during a load, Mulgara does not release the lock on that file.</p>