I do want the option to affect all modules. I handle mixed content. Space removal affects the integrity of my content. 

I remember having a lot of problems with that at first. Most of my modules apply changes to content. I have very few read only modules, and from what I remember, even adding an attribute to an element would mess up the content. I have become obsessive with the chop no option. 

Obsessed or not, I've commented them out just to run a few tests and see if I can still keep my content intact, but now I'm having issues with:

 [bxerr:BASX0003] Unknown serialization parameter "method".

It looks like I'm in for a lot of refactoring before I can test how much the chop option is necessary. Is there a page that explains these new changes, and also how to work with the different types of modules, kind of a quick Best Practices reference. I've been using .xqm exclusively so far. I thought they were necessary to handle the restxq calls. Also, if I don't specify the output method, the .js doesn't know what to do with the result. All in all, it seems like my old practices won't work in the future, but I'm not sure how to tackle this. Some guidance, maybe as a quick example would be welcomed.

Thanks



On Wed, Jul 20, 2016 at 1:46 PM, Christian Grün <christian.gruen@gmail.com> wrote:
Hi France,

> [bxerr:BASX0010] Database option not allowed in library module: chop.

As the error message says, database options cannot be set anymore in
library modules, only in main modules. The reason is that the options
were also affecting other modules, because database options can only
be set globally in the query context.

Generally, it’s advisable to use database options locally. Do you know
which parts of your module were affected by the option?

Cheers
Christian



>
> Does it mean that I no longer need these to keep my spaces intact or is it a
> bug? I didn't find anything in the doc that mention this option being
> removed. I'm still finding the option in the doc with 'false' instead of
> 'no' at http://docs.basex.org/wiki/XQuery_Extensions, and with 'no' at:
> http://docs.basex.org/wiki/XSLT_Module.
>
> I tried changing 'no' to 'false', but it seems that the issue is with the
> option itself, not with the value.
>
>
>
>
> --
> France Baril
> Architecte documentaire / Documentation architect
> france.baril@architextus.com



--
France Baril
Architecte documentaire / Documentation architect
france.baril@architextus.com