Re: [Exist-open] xquery module cache won't let go

[Joe W. <jo...@gm...>]

Thanks for bringing this up, Mike.

I've noticed same phenomenon, and I'm working with build 1.3dev build
9093.  In my case when I make changes an xquery module that I import
into other xqueries (i.e. I save changes to eXist via webdav in
oXygen), the changes aren't recognized unless I restart the server.

I'd be happy to test more if more info would be helpful, but I haven't
known the best way to test this.

- Joe


On Wed, Jun 10, 2009 at 10:56 AM, Mike Sokolov<so...@if...> wrote:
> I ran into a situation where I kept loading an xquery module file into
> the database, but the updates weren't propagating.  At one point I
> deleted the module, but the cached version was still being used.
> Finally I had to restart the database to get my updated query.
>
> The situation was that my query (say query Q) imported a module M (via
> xmldb:exist:///db...) .  I kept updating M, but to no avail.  My guess
> is that query Q was optimized in some way that erased its dependency on
> module M, so that even if M was flushed from the cache, Q was still
> cached and included the old version of M.  Just a guess, but it would
> explain what I saw...
>
> -Mike
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>