Hello Sachit, One of solutions is to handle the long list of properties at the client side:
DESCRIBE ?isbsgProject could be a fast and simple replacement for > > SELECT > > ?isbsgProject*>isbsg:isbsg_project_id as ?isbsg_project_id > > ?isbsgProject*>isbsg:data_quality_rating > as ?data_quality_rating > > ?isbsgProject*>isbsg:ufp_rating as ?ufp_rating > > .... > > ... > Best Regards, Ivan Mikhailov OpenLink Software http://virtuoso.openlinksw.com On Mon, 2011-10-03 at 12:49 +1100, Sachit Malhotra wrote: > Hi Ivan, > > > Thanks for the response. I'll see if i can modify the query and get > less outer joins and see if it fixes the issue. > > > Thanks. > Sachit. > > On Fri, Sep 30, 2011 at 11:05 PM, Ivan Mikhailov > <[email protected]> wrote: > Hello Sachit, > > On Wed, 2011-09-28 at 12:12 +1000, Sachit Malhotra wrote: > > Hi Guys, > > > > > > I am trying to run a query by selecting 240 columns. Here's > how the > > query looks like: > > > > > > prefix isbsg: > > > > <http://localhost:8890/about/id/http/sachit-dev.clearbluewater.com.au:8890/DAV/home/dav/text.csv#> > > SELECT > > ?isbsgProject*>isbsg:isbsg_project_id as ?isbsg_project_id > > ?isbsgProject*>isbsg:data_quality_rating > as ?data_quality_rating > > ?isbsgProject*>isbsg:ufp_rating as ?ufp_rating > > .... > > ... > > ... > > .... > > where > > > { > <http://example.com.au/wsf/datasets/1/example_user_23_27092011020901> > <http://www.example.org/ontology/data/DatasetHasProject> ?exampleProject . }
