Re: Rép. : Re: SPARQL DISTINCT

2014-10-16 Thread Fabian Cretton
yes, working now thanks Fabian >>> Sebastian Schaffert 16.10.2014 10:34 >>> Hi Fabian, this is now fixed. It was a bug in the way function arguments are cast to SQL types. Apparently H2 is a bit more tolerant than PostgreSQL. Greetings, Sebastian 2014-10-16 10:19 GMT+02:00 Sebastian Schaff

Re: Rép. : Re: SPARQL DISTINCT

2014-10-16 Thread Sebastian Schaffert
Hi Fabian, this is now fixed. It was a bug in the way function arguments are cast to SQL types. Apparently H2 is a bit more tolerant than PostgreSQL. Greetings, Sebastian 2014-10-16 10:19 GMT+02:00 Sebastian Schaffert < sebastian.schaff...@gmail.com>: > Hi Fabian, > > I will check, maybe the s

Re: Rép. : Re: SPARQL DISTINCT

2014-10-16 Thread Sebastian Schaffert
Hi Fabian, I will check, maybe the substring semantics in PostgreSQL is different (it does have a different syntax). Greetings, Sebastian 2014-10-16 8:33 GMT+02:00 Fabian Cretton : > Sebastian, > > I just had a try: > The query now works on my installation with the default H2 back-end. > But

Rép. : Re: SPARQL DISTINCT

2014-10-15 Thread Fabian Cretton
Sebastian, I just had a try: The query now works on my installation with the default H2 back-end. But it seems it doesn't work on my PostrgreSQL installation. Sorry that I don't have debug information to give you. >From my trial with this query, without the Distinct: prefix qb:

Rép. : Re: SPARQL DISTINCT

2014-10-15 Thread Fabian Cretton
Thanks, I'll try it first thing tomorrow morning and let you know. Fabian >>> Sebastian Schaffert 15.10.2014 14:45 >>> Hi Fabian, this one was easy: we forgot to implement the substring function. If you update from the GIT develop branch it should work now, can you have a try? Greetings, S

Rép. : Re: SPARQL DISTINCT

2014-10-15 Thread Fabian Cretton
Hi Sebastian, No problem for me to wait for after your ISWC event. Removing the BIND does work, as you suspected: SELECT DISTINCT ?timeStamp WHERE { ?obs a qb:Observation; sdmx-dimension:timePeriod ?timeStamp. } About the logging, I currently have the problem reported here: https://issue