Even after 'optimize', which I believe should allow querying of updated content, content from the db where config was saved through WebDAV is unaccessible for querying.

After a few changes I found that by changing my query, I can make it work.

db:open('AppResources')//*[@id='config']/descendant::*[name()='this-url-base']/node()

works after config.xml is changes through webdav.

db:open('AppResources')//*[@id='config']/descendant::this-url-base/node()

works beofre, but not after config.xml is changed through webdav. Re-optimizing indexes doesn't make the problem go away.

Does this provide an extra clue to the source of the issue?

On Thu, Dec 20, 2012 at 10:53 AM, Christian Grün <christian.gruen@gmail.com> wrote:

Hi France,

ok, got it. One solution that might help you: you could set the
requested system properties before running the BaseXServer, as shown
on the Options page [1] (“Initial values for options…”). Does this
help?

Still, I agree that the solution is a little bit circuitous when
working with WebDAV. I’ve added a GitHub issue to remember your
concern [2]. If you have some more ideas what could help, feel free to
extend the entry.

Best,
Christian

[1] http://docs.basex.org/wiki/Options
[2] https://github.com/BaseXdb/basex/issues/608
___________________________

On Wed, Dec 19, 2012 at 9:08 PM, France Baril
<france.baril@architextus.com> wrote:
> The change is made via Webdav, not via a xquery. Can we set the option for
> all as default? I had assumed that if I set it at DB creation, it would
> remain as is unless changed explicitely. I looked in .basex… can't find this
> option, maybe I should add it? I'm not sure that's the only issue though,
> because even after updating indexes the information from config.xml remains
> unaccessible.
>
> On Wed, Dec 19, 2012 at 7:05 AM, Christian Grün <christian.gruen@gmail.com>
> wrote:
>>
>> Hi France,
>>
>> in the current version, the fulltext index will always get out-of-date
>> when database updates are performed. I have tried to make this more
>> explicit in our documentation [1].
>>
>> Before adding new documents, you may set database options in your
>> query via option declarations [2]…
>>
>> declare option db:addraw 'true';
>> db:add(....)
>>
>> …or pragmas [2]…
>>
>> (# db:addraw true #) {
>> db:add(....)
>> }
>>
>> Maybe this helps?
>> Christian
>>
>> [1] http://docs.basex.org/wiki/Indexes#Updates
>> [2] http://docs.basex.org/wiki/Options
>> ________________________________________________
>>
>> > The file is saved correctly, however if I look at the database
>> > properties,
>> > only the parsing properties remain intact. Full text indexes are
>> > out-dated
>> > and indexing is turned OFF. Moreover, Add remaining files as raw files
>> > goes
>> > back to default [we need it ON] and parse files in archives goes back to
>> > default ON [we need it OFF].
>> >
>> > I just tried it on 7.5 and got the same result.
>> >
>> >
>> > On Tue, Dec 18, 2012 at 8:27 AM, Christian Grün
>> > <christian.gruen@gmail.com>
>> > wrote:
>> >>
>> >> Hi France,
>> >>
>> >> I’m still not sure what may be the core problem..
>> >>
>> >> > From Oxygen, we access the DataSource view that has a connection to
>> >> > AppResources and open /configs/config.xml
>> >> > We make/save changes.
>> >> > Access our content, everything that should have come from the config
>> >> > file is missing. We conclude, we made a bad change.
>> >>
>> >> does this mean that your file will not be saved by oXygen, or
>> >> incorrectly saved? What happens if you close and reopen the config.xml
>> >> file after saving it in oXygen?
>> >>
>> >> Best,
>> >> Christian
>> >> _____________________________________
>> >>
>> >> > We make the same change to the config.xml that is on our file system
>> >> > We create/override the AppResources DB.
>> >> > Access our content. It works.
>> >> >
>> >> > No matter what the change is, if the modification is made on the
>> >> > config.xml that is in the DB, it breaks. If the modification is made
>> >> > on the
>> >> > file system, and then the DB is overridden, it works. Even if we
>> >> > force
>> >> > reindexing of the DB after the changes, the .xqm accessing the config
>> >> > file
>> >> > get empty results.
>> >> >
>> >> >
>> >> >
>> >> > On Mon, Dec 10, 2012 at 5:20 PM, Christian Grün
>> >> > <christian.gruen@gmail.com> wrote:
>> >> >>
>> >> >> Hi France,
>> >> >>
>> >> >> I’m not sure what could be helpful for this particular case.. If I
>> >> >> get
>> >> >> it right, your xqm config file is not stored in the database, but in
>> >> >> the webapp, which you are editing from within oXygen and requesting
>> >> >> via RESTXQ, right? What happens if you manually edit the xqm file
>> >> >> outside oXygen?
>> >> >>
>> >> >> Best,
>> >> >> Christian
>> >> >> ___________________________
>> >> >>
>> >> >> > Our .xqm uses a configuration file that is stored in a DB called
>> >> >> > AppResources.
>> >> >> >
>> >> >> > When we use the GUI to create/upload the content for AppResources,
>> >> >> > we
>> >> >> > can
>> >> >> > access our restxq pages and the result is based on our config.
>> >> >> >
>> >> >> > If we access the config file in Oxygen and change anything, even a
>> >> >> > space,
>> >> >> > it's like the .xqm cannot access the information anymore.
>> >> >> >
>> >> >> > We tried:
>> >> >> >
>> >> >> > Updating/optimize the index/paths.
>> >> >> > Stopping/starting the server.
>> >> >> >
>> >> >> > The file is saved properly. If we save it on disk from Oxygen and
>> >> >> > reload
>> >> >> > AppResources with the config file, we are able to access the
>> >> >> > information in
>> >> >> > the file again. So the issue is really the fact that the change
>> >> >> > occurs
>> >> >> > through webdav.
>> >> >> >
>> >> >> > What are we missing here?
>> >> >> >
>> >> >> > Regards,
>> >> >> >
>> >> >> > France
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > France Baril
>> >> >> > Architecte documentaire / Documentation architect
>> >> >> > france.baril@architextus.com
>> >> >> > (514) 572-0341
>> >> >> >
>> >> >> > _______________________________________________
>> >> >> > BaseX-Talk mailing list
>> >> >> > BaseX-Talk@mailman.uni-konstanz.de
>> >> >> > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
>> >> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > France Baril
>> >> > Architecte documentaire / Documentation architect
>> >> > france.baril@architextus.com
>> >> > (514) 572-0341
>> >
>> >
>> >
>> >
>> > --
>> > France Baril
>> > Architecte documentaire / Documentation architect
>> > france.baril@architextus.com
>> > (514) 572-0341
>
>
>
>
> --
> France Baril
> Architecte documentaire / Documentation architect
> france.baril@architextus.com
> (514) 572-0341

--
France Baril
Architecte documentaire / Documentation architect
france.baril@architextus.com
(514) 572-0341