Re: [SMW-devel] {{#ask}}

2007-12-29 Thread cnit
What I meant was: a simple cron-job can touch LocalSettings.php regularly to purge the MW cache globally. Not much interaction with MW needed for that. Yes, that's simple. I guess a strong solution for that will still take some time. One could of course store inline queries in some table, use

Re: [SMW-devel] [PATCH] Support LIKE in queries

2007-12-29 Thread Markus Krötzsch
On Samstag, 29. Dezember 2007, DanTMan wrote: A lot of people are accustomed to the ? (single-character match) and * (multi-character match) format. It would be easy to escape the '_'s and '%'s in a match and then do a replace of ? to _ and * to %. (A little preg and \ could still easily

Re: [SMW-devel] SMW Performance

2007-12-29 Thread Markus Krötzsch
On Freitag, 28. Dezember 2007, Lau, William (NIH/CIT) [E] wrote: We have a set of semantic queries in a template. That template is used in some pages. However, by looking at the database process list, it seems that those set of queries are processed whenever a page is requested, even when the

Re: [SMW-devel] Performance: (Was: {{#ask}})

2007-12-29 Thread Markus Krötzsch
On Montag, 17. Dezember 2007, Sergey Chernyshev wrote: Thank you, Markus - it's a really good review! I wonder if there is any way to unify performance reporting for all SMW instances so we can compare the effects of large data sets, different systems configs (e.g. disabled cache and so on) -

Re: [SMW-devel] [PATCH] Support LIKE in queries

2007-12-29 Thread DanTMan
^_^ ok, I thought we escaped with a \, which isn't something that normal users would find easy to use. But a starting space escape is ok. I still would pick ~ as the best thing for use of REGEX and prefer a different operator for wild cards I guess the % is probably best for the wild card

Re: [SMW-devel] {{#ask}}

2007-12-29 Thread Sergey Chernyshev
I'm not sure if restricting Ask functionality is along the lines of Wikipedia policies - it's not a modification operation therefore it should be public, I believe. I agree, that abuse bocking and request throttling might be a solution here, but in general, I wouldn't recommend restriction of

Re: [SMW-devel] SMW Performance

2007-12-29 Thread Sergey Chernyshev
Hmm. I didn't realize there is a way to remove $smwgQDefaultNamespaces restriction and this will enable all namespaces instead of disabling them. Why is it that this setting not set to NULL by default then? I don't see any point in restricting namespaces unless it's absolutely necessary for