The behavior you describe is normal: you'll see similar behavior with built-in databases like Schemas, Security, and Triggers.
The schemas-database setting tells the database where to look for schema imports. For a custom schemas database, I think you'll only care about its own schemas-database if your schemas import other schemas. If so, you can and should set the new schemas database to refer to itself. -- Mike On 19 Oct 2012, at 23:08 , "Tim Meagher" <[email protected]> wrote: > Hi Folks, > > I am creating a second schemas database on a server. I noticed that the > default Schemas database refers to itself (which seems kind of odd), e.g., > > database name > > The database name. > security database > > The security database. > schema database > > The database that contains schemas. > triggers database > If I create a new schemas database, should it also refer to itself and if so, > why? Is there any problem configuring it to point to the default Schemas > database? > > Thank you! > > Tim Meagher > > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
