Dan,
As far as I know, the compression option has been removed, because it was not properly implemented, and it caused some data damage.
There are some examples, in the documentation, that use it, setting the "gzip" and the "compression" attribute in the collection configuration, but my understanding is that those attributes have no effect if used with XIndice 1.0.
Francesco
Is there something else that I can do to get the size of the database down? Am I missing something really obvious, like a call to optimize or compress the data somewhere?
This just won't scale for me with its current behavior, so I hope I'm doing something wrong. If I'm not, does anyone have any suggestions for an XML database that scales better?
Thanks,
Dan
- Francesco Bellomi "Use truth to show illusion, and illusion to show truth."
