I agree - it is an issue since the beginning and it'll be great if this
issues was approached for fixing, but it definitely wasn't fixed before or I
would've noticed ;)

Markus, do you think it's possible to create a dependency tables for all
query results which are checked upon page updates and invalidate the cache?

This will not completely fix the issue as query results might not contain
something which will be added when page is updated, although you can add
just property names to the dependency table so it always invalidates when
this property is updayed, but even partial solution will be good enough.

       Sergey


On Fri, Jul 25, 2008 at 2:44 AM, Markus Krötzsch <
[EMAIL PROTECTED]> wrote:

> On Freitag, 25. Juli 2008, Steren wrote:
> > Hello,
> > I played a bit with my local installation of SMW 1.2 and SMWsvn and
> noticed
> > a bug : Inline queries don't refresh after the deletion of a property.
> >
> > Here is the basic scenario : (This behavior can be reproduced on the
> > sandbox http://sandbox.semantic-mediawiki.org/wiki/Testpage )
> > - Add properties to pages
> >    in my example : [[check::1]] for Page1check and [[check::2]] for
> > Page2check
> > - add a query for these properties to a page
> >    for me : {{#ask: [[check::+]]}} on Testpage
> > - remove one property from one of the first pages
> >    let's remove [[check::1]] on Page1check
> > - The page with the query still displays the erased property unless you
> > re-edit it.
> >
> > I'm sure this behaviour didn't exist in SMW 1.1.2.
>
> Sorry, but I am sure it did.
>
> > I wanted to raise this issue on the list, because if you can confirm,
> this
> > should be corrected as soon as possible.
>
> The page with the query result is completely cached by MediaWiki, as a
> static
> output that is no longer associated with any query or other parser function
> features. SMW has never had a mechanism for invalidating pages caches to
> refresh queries. We do not even check if properties actually changed in an
> edit (this would require more work to compare the current storage contents
> to
> the new input).
>
> Page cache purging is randomised, so you may have got suitable results by
> chance. It is also possible, especially on small wikis, to just disable the
> MediaWiki cache to avoid such effects.
>
> Regards,
>
> Markus
>
> >
> > sincerely,
> > Steren
>
>
>
> --
> Markus Krötzsch
> Semantic MediaWiki    http://semantic-mediawiki.org
> http://korrekt.org    [EMAIL PROTECTED]
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Semediawiki-devel mailing list
> Semediawiki-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
>
>


-- 
Sergey Chernyshev
http://www.sergeychernyshev.com/
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel

Reply via email to