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 escape those.)
I don't know about ~ though, in the la
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 template is not used by the requested page
(e.g. special pages). All t
On Freitag, 28. Dezember 2007, Yaron Koren wrote:
> How about ~%substring% instead? The "~" is the symbol for pattern matching
> in Perl and some UNIX languages, and it might be a clearer indicator of
> function than "%".
>
I would immediately use that, but IFRC the Halo extension has a similar sy
On Freitag, 28. Dezember 2007, cnit wrote:
> > Well, that is not the case for the current parser cache, neither in MW
> > nor in SMW. But if course it could be achieved with some server-side
> > cronjobs.
>
> Ah, I didn't knew about MW cronjobs. That sounds nice. Will try to
> find out some example
How about ~%substring% instead? The "~" is the symbol for pattern matching
in Perl and some UNIX languages, and it might be a clearer indicator of
function than "%".
-Yaron
On Dec 27, 2007 2:16 PM, Markus Krötzsch <[EMAIL PROTECTED]> wrote:
> Thanks. I have applied the patch, and added a way of
> Well, that is not the case for the current parser cache, neither in MW nor in
> SMW. But if course it could be achieved with some server-side cronjobs.
Ah, I didn't knew about MW cronjobs. That sounds nice. Will try to
find out some examples. Maybe you're right that such functionality
shouldn't b
> Forget my previous post. The problem goesaway when I removed one
> template. It seems the performance issue is related tothe
> application instead of the database.
Try setting up eAccelerator for PHP, maybe it would help a bit. Also,
I believe that MW/SMW requires dedicated server (co-location).
On Donnerstag, 27. Dezember 2007, cnit wrote:
> > (2) Query answering is done without any caching, and this is clearly a
> > problem. While inline queries are computed only once and stored in the
> > parser cache afterwards, Special:Ask has no caching facility at all. This
> > needs to change in th
