still fails , but more explicit debugging in the output:

org.h2.jdbc.JdbcSQLException: Column count does not match; SQL statement:\n

Caused by: org.h2.jdbc.JdbcSQLException: Column count does not match; SQL
statement:
SELECT U1.U1 AS V1, U1.U2 AS V2
 FROM ((SELECT P1.object AS U1, P2.object AS U2, NULL AS U4, NULL AS U3
 FROM triples P1
 LEFT JOIN
  triples P2 ON (P2.deleted = false
      AND P1.object = P2.subject
      AND P2.predicate = 738710905965015040)
 WHERE P1.deleted = false
      AND P1.subject = 738711452851924992
      AND P1.predicate = 738710906002763776

 ) UNION (SELECT NULL AS U1, NULL AS U2
 FROM ((SELECT NULL AS U2, P1.object AS U1
 FROM triples P1
 WHERE P1.deleted = false
      AND P1.subject = 738711452851924992
      AND P1.predicate = 738710905965015040

 ) UNION (SELECT P1.object AS U2, NULL AS U1
 FROM triples P1
 WHERE P1.deleted = false
      AND P1.subject = 738711452851924992
      AND P1.predicate = 738711452872896512

 )) AS U1
 )) AS U1

On Fri, 3 Jun 2016 at 20:02 Sergio Fernández <[email protected]> wrote:

> On Fri, Jun 3, 2016 at 10:35 AM, Rob Atkinson <[email protected]>
> wrote:
> >
> > i'm very busy the next few weeks - but if you can point me to a download
> > for the 3.4 snapshot I'll give it a go.
>
>
> Just:
>
> 1) git clone [email protected]:apache/marmotta.git
> 2) cd marmotta/launchers/marmotta-webapp
> 3) mvn tomcat7:run
> 4) configure postgres as db
> 5) make your test
>
> Thanks!
>
>
>
>
> > On Fri, 3 Jun 2016 at 16:52 Sergio Fernández <[email protected]> wrote:
> >
> > > Maybe it's a bug how our SPARQL engine translate SPARQL into SQL...
> > > Have you test it against 3.4.0-SNAPSHOT? Please, do it and file a jira
> if
> > > it also fails.
> > >
> > > On Fri, Jun 3, 2016 at 8:07 AM, Rob Atkinson <[email protected]>
> > > wrote:
> > >
> > > > Hi
> > > >
> > > > (although I previously created a couple of issues I dont seem to be
> > able
> > > to
> > > > create one now - no option on dashboard.)
> > > >
> > > >
> > > > Anyway I have a query that is valid and works against Sesame that
> > > Marmotta
> > > > 3.3 complains about:
> > > >
> > > > PREFIX  dcterms: <http://purl.org/dc/terms/>
> > > > PREFIX  rdfs: <http://www.w3.org/2000/01/rdf-schema#>
> > > > PREFIX  void: <http://rdfs.org/ns/void#>
> > > > PREFIX  rdf:  <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
> > > > PREFIX  lid:  <http://id.sirf.net/def/schema/lid/>
> > > >
> > > > SELECT *
> > > > WHERE
> > > >   {   { { <http://resources.opengeospatial.org/def/voc/examples/mdg>
> > > > rdf:type ?___0 }
> > > >         OPTIONAL
> > > >      { { ?___0 rdfs:label ?___1 } }
> > > >       }
> > > >     UNION
> > > >       { <http://resources.opengeospatial.org/def/voc/examples/mdg>
> > > > rdfs:label ?___2 }
> > > >     UNION
> > > >       { <http://resources.opengeospatial.org/def/voc/examples/mdg>
> > > > void:sparqlendpoint ?___10 }
> > > >     }
> > > >
> > > > If you remove any one of the UNION clauses it works.
> > > >
> > > > The error comes from the underlying postGres:
> > > > org.openrdf.query.QueryEvaluationException:
> > > > org.postgresql.util.PSQLException: ERROR: each UNION query must have
> > the
> > > > same number of columns
> > > >
> > > > maybe this is an openrdf problem - but it works fine under Sesame -
> so
> > > > maybe its a version thing?
> > > >
> > > > Cheers
> > > >
> > >
> > >
> > >
> > > --
> > > Sergio Fernández
> > > Partner Technology Manager
> > > Redlink GmbH
> > > m: +43 6602747925
> > > e: [email protected]
> > > w: http://redlink.co
> > >
> >
> > --
> > Sergio Fernández
> > Partner Technology Manager
> > Redlink GmbH
> > m: +43 6602747925
> > e: [email protected]
> > w: http://redlink.co
> >
>

Reply via email to