couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Lehnardt (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (COUCHDB-201) per-database configuration
Date Fri, 09 Jan 2009 18:07:59 GMT

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

Jan Lehnardt reassigned COUCHDB-201:
------------------------------------

    Assignee: Jan Lehnardt

> 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.9
>
>
> 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.


Mime
View raw message