[COUCHDB-1004] list_to_existing_atom is too restrictive as used by couch_rep

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.0.3, 1.1
• Component/s: Replication

Environment

erlang

• Skill Level: New Contributors Level (Easy)
• Assignee: Unassigned
• Reporter: Bob Dionne
• Created: 02/Jan/11 13:05
• Updated: 20/Apr/11 10:47
• Resolved: 20/Apr/11 10:47

Description

We'd like to additional information to db_info in BigCouch, such as the Q and N constants for a given database. This causes replication to fail when replicating from BigCouch to CouchDB due to the use of list_to_existing_atom in couch_rep:dbinfo(...

The claim is that list_to_atom pollutes the atoms table, however superficial testing indicates this is not the case, list_to_atom when called repeatedly seems to work fine. If this is true then consider reverting list_to_existing_atom back to list_to_atom.