couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Kocoloski (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-355) deleting a _config key sets the value to ""
Date Sun, 19 Jul 2009 20:21:14 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733061#action_12733061
] 

Adam Kocoloski commented on COUCHDB-355:
----------------------------------------

Not only that, we'd have to keep track of all the times a given Key appears in the configuration
chain and delete all of them.

It would probably be easier (if more confusing) to interpret an empty value in the config
file to mean DELETE.

> deleting a _config key sets the value to ""
> -------------------------------------------
>
>                 Key: COUCHDB-355
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-355
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>    Affects Versions: 0.9
>            Reporter: Adam Kocoloski
>            Assignee: Adam Kocoloski
>
> couch_config:delete/2 is implemented as
> delete(Section, Key) ->
>     set(Section, Key, "").
> I think that's misleading -- a key with an empty value is not the same as no key at all.
 Consider the case of an update_notification process.  To me, deleting that key should just
send an EOF to the process.  Instead Couch sends the EOF and then tries to spawn an os_process
to execute "".  The end result is the same, but a few things crash along the way.

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