Re: [Exist-open] Where Does eXist Content Live and Bulk Erasure

[Randall R S. <rs...@so...>]

Wolfgang,

Thanks for the pointers.


On Wednesday 29 November 2006 12:51, Wolfgang Meier wrote:
> > 1) Where is the XML content I add to an eXist instance stored?
>
> By default, eXist stores its database files into webapp/WEB-INF/data.
>
> > 1a) Can I configure where content is stored?
>
> Yes, see the "file" and "journal-dir" settings in conf.xml.

OK. It looks as though that file, as shipped, contains much more 
documentation than configuration, so I should have no trouble figuring 
it out.


> > 2) What's the easiest, fastest and most reliable way, short of
> > reinstalling, to do bulk erasures of broad swathes of stored
> > content?
>
> Just remove the content of the webapp/WEB-INF/data directory while
> the db is shut down. The files will be recreated next time you start
> the db.

That will eradicate everything. Is there a way, perhaps via the 
management console Web interface, to, say, recursively remove select 
collection hierarchies? Or should I just write some generic content 
maintenance tools? Perhaps such tools exist out there somewhere?


> > I assume the answer to (1) depends on whether I'm using the
> > stand-alone or the WAR-file / servlet-hosted deployment.
>
> It's the same directory for both deployments.

OK.


> Wolfgang


Thanks again.

Randall Schulz