Thanks to both of you, Fabrice and Christian. I should have asked this question a long time ago - it will help a lot with organizing my work better.
Jonathan On Tue, Feb 6, 2018 at 5:41 PM, Fabrice ETANCHAUD < fetanch...@pch.cerfrance.fr> wrote: > Jonathan, in my humble opinion, here are the main reasons you may need > several collections : > > > > - FullText indexing in several languages (because language is > collection wide) : a per language partition of your data > > - Size (usually in number of nodes) limitation > > - Huge updates : a read only backlog collection + a read/write > front collection of fresh data + queries tailored to read both collections. > > > > Best regards, > > And maybe good night ? > > > > Fabrice Etanchaud > > > > *De :* basex-talk-boun...@mailman.uni-konstanz.de [mailto: > basex-talk-boun...@mailman.uni-konstanz.de] *De la part de* Jonathan Robie > *Envoyé :* mardi 6 février 2018 23:31 > *À :* BaseX > *Objet :* [basex-talk] One document per database or multiple? > > > > If I have a set of related documents (a text, a lexicon, frequency counts, > a discourse analysis, etc), how should I decide when to put more than one > document in a single database at different paths, as opposed to putting one > document in each database? > > > > When I create a database from the GUI, it seems to prefer one document per > database. Should I take that as a hint? > > > > Jonathan >
