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] [Resolved] (COUCHDB-201) per-database configuration
Date Sun, 17 Apr 2011 11:16:05 GMT

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

Jan Lehnardt resolved COUCHDB-201.
----------------------------------

       Resolution: Not A Problem
    Fix Version/s:     (was: 1.2)

The concrete feature request can be solved with /_changes now.

Per-DB configuration can still make sense for other things, but I'd like to see a concrete
problem description first.

> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message