Hi Christian,
> maybe this is due to the beta version you are working with? That is easy to test - and I will do that. I just wanted to make sure I hadn’t misunderstood what I *should* see. I will let you (and the list know) the outcome of my test. Many thanks, James > On Mon, Nov 30, 2015 at 4:56 PM, James Ball <basex-t...@jamesball.co.uk> > wrote: >> Hello, >> >> I’m trying out AUTOOPTIMIZE for the first time and I’m not getting what I >> expect. >> >> Running: BaseX 8.3 beta ec9b627 >> >> A new database is created with a single document which has TEXTINDEX, >> ATTRINDEX, UPDINDEX and AUTOOPTIMISE all set to true. >> >> This is what INFO DATABASE shows (as I expect): >> >> Indexes >> Up-to-date: true >> TEXTINDEX: true >> ATTRINDEX: true >> FTINDEX: false >> TEXTINCLUDE: >> ATTRINCLUDE: >> FTINCLUDE: >> LANGUAGE: English >> STEMMING: false >> CASESENS: false >> DIACRITICS: false >> STOPWORDS: >> UPDINDEX: true >> AUTOOPTIMIZE: true >> MAXCATS: 100 >> MAXLEN: 96 >> >> Now I add a new document (or more than one) to the database. I expect that >> Up-to-date will still be true and that AUTOOPTIMIZE will still be true. But >> what I see is both are now false: >> >> Indexes >> Up-to-date: false >> TEXTINDEX: true >> ATTRINDEX: true >> FTINDEX: false >> TEXTINCLUDE: >> ATTRINCLUDE: >> FTINCLUDE: >> LANGUAGE: English >> STEMMING: false >> CASESENS: false >> DIACRITICS: false >> STOPWORDS: >> UPDINDEX: true >> AUTOOPTIMIZE: false >> MAXCATS: 100 >> MAXLEN: 96 >> >> Perhaps this is the expected behaviour and I’ve misunderstood AUTOOPTIMIZE? >> Or is there a bug? >> >> Many thanks, James
