From: Leyne, S. <Se...@br...> - 2009-10-26 21:07:37
|
> > "So, if I move my database to another server/folder, I will need to move > the separate conf file as well!" > > Is it the real problem? Place the appropriate .conf file next to the > database file and you're unlikely to forget it when moving... > > > In this way the database owner can define his configuration, while the > server/host manager can define his settings. > > I can easily imagine a database configured by the owner to be > unmanageable on many hosts, regardless of what the server manager thinks > about it... OK, that's a fair point/comment but that doesn't speak to issue at hand, where should the database settings be stored. If we want to talk about limiting the scope of the database setting, then we should talk about adding new parameters to define the min/max values which are appropriate for a server. Such, that if a server has min = 10 and max = 100, if a database had a setting of 150, then it would be limited to 100. But if that database was moved to another server, which had a max = 200, then the database setting would be "fine". Sean |