GitHub user jaydoane opened a pull request:

    https://github.com/apache/couchdb-couch/pull/129

    2898 improve global changes tests

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cloudant/couchdb-couch 
2898-improve-global-changes-tests

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-couch/pull/129.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #129
    
----
commit c7ecd2b46601ce83177be333252f7a62aa5277ff
Author: Jay Doane <[email protected]>
Date:   2015-11-22T18:56:44Z

    Create and delete test db using HTTP API
    
    This supports downstream name munging that might occur
    
    COUCHDB-2898

commit 5df95158d00bb0a72f62b13d9468dd47e5c6b95d
Author: Jay Doane <[email protected]>
Date:   2015-11-22T19:01:04Z

    Ensure _global_changes exists
    
    Downstream builds automatically ensure _global_changes exists, so this 
commit works for both cases
    
    COUCHDB-2898

commit e7b3ba4319367cbe26838491d730fc9dc27be1a0
Author: Jay Doane <[email protected]>
Date:   2015-11-22T19:07:18Z

    Replace "/" in db name with "-"
    
    Unfortunately, the slash causes certain downstream builds to generate 
incorrect db_names in the _db_updates results.
    
    This change still demonstrates that some non-alphanumeric characters are 
allowed in db names, while removing the
    specific character that triggers downstream incompatibility.
    
    COUCHDB-2898

commit a2e6dc919f3bd79efc4e423fc039f393b0240206
Author: Jay Doane <[email protected]>
Date:   2015-11-22T19:09:29Z

    Simplify, and remove unnecessary code
    
    COUCHDB-2898

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to