Issue87

Title SPARQL Filters need access to all bindings
Priority feature Status deferred
Superseder Nosy List alerer
Assigned To Topics

Created on 2006-08-03.11:39:21 by alerer, last changed 2007-07-09.14:06:40 by connolly.

Messages
msg501 (view) Author: connolly Date: 2007-07-09.14:06:40
cleaning up assignments for summer 2007 project management
msg209 (view) Author: connolly Date: 2006-08-03.17:47:13
the limitation of one constraint per var doesn't allow, e.g. "after the 1st and
before the 15th"
msg182 (view) Author: alerer Date: 2006-08-03.11:39:21
They're oh-so-bad. They need to be rearchitectured to be much more general, i.e.
take in the entire set of bindings, instead of directly acting on one binding.
This would also fix the problem with the hash from variables to filters, which
limits the filters on a variable to 1.

What we need is just an array of filters that the set of bindngs is checked
against every time a new variable is bound. This will slow down the query, but
what can you do.
History
Date User Action Args
2007-07-09 14:06:40connollysetstatus: chatting -> deferred
assignedto: alerer ->
messages: + msg501
2006-08-03 17:47:14connollysetstatus: unread -> chatting
messages: + msg209
2006-08-03 15:34:31connollysettitle: SPARQL Filters -> SPARQL Filters need access to all bindings
2006-08-03 11:39:21alerercreate

To request an account, email [name of this project]@csail.mit.edu.