You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Jan Lehnardt (JIRA)" <ji...@apache.org> on 2009/03/23 18:37:50 UTC

[jira] Updated: (COUCHDB-201) per-database configuration

     [ https://issues.apache.org/jira/browse/COUCHDB-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Lehnardt updated COUCHDB-201:
---------------------------------

    Fix Version/s:     (was: 0.9)
                   0.10

> per-database configuration
> --------------------------
>
>                 Key: COUCHDB-201
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-201
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Database Core
>    Affects Versions: 0.9
>            Reporter: Brian Palmer
>            Assignee: Jan Lehnardt
>            Priority: Minor
>             Fix For: 0.10
>
>
> I have one large database that contains only one document type that I need to run an update_notification script on, but I'd really rather the script not have to get triggered for the other databases as well.
> It'd be a huge improvement if you could specify per-database configuration in the .ini file. Probably not for all options does it make sense (address, port come to mind) but a few of the key options that I think it would really make sense for:
> * external processes
> * update_notifications
> * database_dir

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.