_purge URI returns DB update seq instead of purge seq
-----------------------------------------------------
Key: COUCHDB-663
URL: https://issues.apache.org/jira/browse/COUCHDB-663
Project: CouchDB
Issue Type: Bug
Components: Database Core
Environment: trunk / 0.11
Reporter: Filipe Manana
Fix For: 0.11
Attachments: couchdb-663-trunk.patch
>From the email sent by Markus Jelsma, on the 22 February 2010, to the users
>list:
"
purge_seq gets incremented for each _purge request. But there is a small
issue:
# curl -X GET http://localhost:5984/idm/
{"db_name":"idm","doc_count":7,"doc_del_count":0,"update_seq":27,"purge_seq":12,"compact_running":false,"disk_size":110680,"instance_start_time":"1266831271770843","disk_format_version":4}
# curl -X POST http://localhost:5984/idm/_purge -d '{}'
{"purge_seq":28,"purged":{}}
# curl -X GET http://localhost:5984/idm/
{"db_name":"idm","doc_count":7,"doc_del_count":0,"update_seq":28,"purge_seq":13,"compact_running":false,"disk_size":114776,"instance_start_time":"1266831271770843","disk_format_version":4}
# curl -X POST http://localhost:5984/idm/_purge -d '{}'
{"purge_seq":29,"purged":{}}
Check it out! Purging returns update_seq instead.
"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
