From: Dmitriy S. <sha...@gm...> - 2011-02-17 11:54:16
|
On Thu, Feb 17, 2011 at 3:04 PM, Stefan Majewski < ste...@un...> wrote: > On 17/02/11 09:26, Adam Retter wrote: > >> I really feel that this *must* go in /db/system. As a user I dont >> really want my databases becoming polluted with configuration files >> that are not part of my application. >> > > I really do second this. I use the collection name "etc" in several/most > applications, as I usually need a place to put my App's configuration. Then, > in case I deploy the application to my top-level database directory (what I > rarely do, but nonetheless) I would probably face a conflict. From a user > perspective this seems to be just another name to avoid. > That is what it for .... mean pluggable applications ... what permissions do you set to this collection? and it should not generate any conflicts, because on restore permissions can be changed any way. All I need is collection that exist by default and pluggings don't need to worry about. -- Dmitriy Shabanov |