Hi,
I'm looking now into adding SMWSQLStore3 support to Semantic Forms,
finally. (I should note that, once this is done, I believe all of my
extensions will fully support SMWSQLStore3.)
I'm pretty sure that there's only one place in the SF code that needs to be
updated to support SMWSQLStore3 - in the code that handles remote
autocompletion, which does direct SQL querying. This code has to find, for
any substring, the set of values that either start with that string, or
have a word that starts with that string. So, for instance, if the user
types "ab", the autocompletion should return "About us" or "Personal
abilities", but not "Cabs".
(It's not an issue for regular, local autocompletion, because there the
Javascript takes care of the matching.)
I'm pretty sure that there's no way to get this set of results using a
regular SMW query. Assuming that's true, there are a few possibilities:
1) Add additional SQL to support the new database structure of SMWSQLStore3.
2) Add to SMW's querying capabilities to support this kind of matching.
Maybe syntax like this could work:
{{#ask:[[property-name::~substring]]
|+wordmatching
|?property-name}}
3) Change SF's autocompletion (either just the remote autocompletion, or
both kinds) to match arbitrarily on any part of the string, not just the
beginnings of words. This is really a question for the users - personally,
I like the matching on words, but other people might not feel as strongly
about it.
Any thoughts?
-Yaron
--
WikiWorks · MediaWiki Consulting · http://wikiworks.com
------------------------------------------------------------------------------
Keep yourself connected to Go Parallel:
TUNE You got it built. Now make it sing. Tune shows you how.
http://goparallel.sourceforge.net
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel