On Sun, Jan 2, 2011 at 1:48 PM, Robert Dionne
wrote:
> Klaus,
>
> perhaps I just heard wrong or misinterpreted what was said in the chat
> room. It did seem unusual that calling list_to_atom("foo") twice would add
> more than one atom.
I was wrong about that. I had the idea that I saw or hear
Klaus,
perhaps I just heard wrong or misinterpreted what was said in the chat room.
It did seem unusual that calling list_to_atom("foo") twice would add more than
one atom. So just reverting the call back in couch_rep:dbinfo should suffice to
fix this as it's internal. Thanks,
Bob
On Jan
As far as I can remember, the motivation behind list_to_existing_atom
was not the fact that list_to_atom pollutes the atoms table during
normal operation. However, it won't prevent atom table pollution when
something goes wrong or somebody goes malicious (i.e., DoS attack).
I've just looked it up
list_to_existing_atom is too restrictive as used by couch_rep
-
Key: COUCHDB-1004
URL: https://issues.apache.org/jira/browse/COUCHDB-1004
Project: CouchDB
Issue Type: Bug
