Ah alright,

Oops had it in plain sight all along "Added with Version 8.0".

Sorry. I read some mail messages about it and assumed it applied to the 7 branch.

I will try the snapshot.

Thanks,

--Marc



On Tue, Jul 15, 2014 at 1:08 PM, Christian GrĂ¼n <christian.gruen@gmail.com> wrote:
Hi Marc,

as the MIXUPDATES option is a greater change in our updating
architecture, it will only be introduced with BaseX 8.0 [1]. Feel free
to check out the latest snapshot [2]!

Christian

[1] http://docs.basex.org/wiki/Options#MIXUPDATES
[2] http://files.basex.org/releases/latest



On Tue, Jul 15, 2014 at 1:05 PM, Marc van Grootel
<marc.van.grootel@gmail.com> wrote:
> This is with basex 7.9 on Windows
>
> I am trying to get (RESTXQ) queries to run with MIXUPDATES.
>
> I tried adding MIXUPDATES = true to each of the sections in the .basex file.
> For all but the last section (# Local Options) the MIXUPDATES line would be
> deleted upon startup of basexhttp.bat
>
> So if I would add the line to the top under # General Options and then start
> the http server I would get:
>
>>basexhttp -d
> C:/apps/basex/.basex: Unknown option 'MIXUPDATES'.
> C:/apps/basex/.basex: writing new configuration file.
> DEBUG: true
> PASSWORD: admin
> USER: admin
> DEBUG: true
> WEBPATH: F:\home\data\basex\webapp
> BaseX 7.9 [Server]
> Server was started (port: 1984)
> HTTP Server was started (port: 8984)
>
> When I put it under # Local Options it won't complain but it won't pick up
> MIXUPDATES so my queries still fail.
>
>>basexhttp -d
> DEBUG: true
> PASSWORD: admin
> USER: admin
> DEBUG: true
> WEBPATH: F:\home\data\basex\webapp
> BaseX 7.9 [Server]
> Server was started (port: 1984)
> HTTP Server was started (port: 8984)
>
> Am I doing something wrong here?
>
> --Marc



--
--Marc