CouchDB Notice for 1.0.1 - Potential Data Loss
couchdb.apache.org
CouchDB Notice for 1.0.1 - Potential Data Loss
1–10 of 33 posts
Re: CouchDB Notice for 1.0.1 - Potential Data Loss
#2I should make clear that the notice is titled "Notice for 1.0.1" because the 1.0.1 release (due this week) will contain the fix. The bug is confined to 1.0.0.
Re: CouchDB Notice for 1.0.1 - Potential Data Loss
#3I should make clear that the notice is titled "Notice for 1.0.1" because the 1.0.1 release (due this week) will contain the fix. The bug is confined to 1.0.0.
I hope next time Damien will think twice before insulting other databases for having similar issues:
Re: CouchDB Notice for 1.0.1 - Potential Data Loss
#4I should make clear that the notice is titled "Notice for 1.0.1" because the 1.0.1 release (due this week) will contain the fix. The bug is confined to 1.0.0.
I hope next time Damien will think twice before insulting other databases for having similar issues: https://twitter.com/damienkatz/status/15444148375
Good find--I was going to look for it myself.
Re: CouchDB Notice for 1.0.1 - Potential Data Loss
#5I should make clear that the notice is titled "Notice for 1.0.1" because the 1.0.1 release (due this week) will contain the fix. The bug is confined to 1.0.0.
I hope next time Damien will think twice before insulting other databases for having similar issues: https://twitter.com/damienkatz/status/15444148375
As I saw the tweet I became uneasy, followed the link and, sure enough, it's my post he's referencing. That's a bit disconcerting, I feel responsible for trashing MongoDB all over the internet. At least my conscience is lighter because everything I wrote was true...
Re: CouchDB Notice for 1.0.1 - Potential Data Loss
#6Earlier quoted context omitted.
I hope next time Damien will think twice before insulting other databases for having similar issues: https://twitter.com/damienkatz/status/15444148375
As I saw the tweet I became uneasy, followed the link and, sure enough, it's my post he's referencing. That's a bit disconcerting, I feel responsible for trashing MongoDB all over the internet. At least my conscience is lighter because everything I wrote was true...
Yes, it was true that the 32bit version of mongodb that is limited to 2gb would lose your data if you injected more than 2gb in it, shame on mongodb...
Re: CouchDB Notice for 1.0.1 - Potential Data Loss
#7Earlier quoted context omitted.
As I saw the tweet I became uneasy, followed the link and, sure enough, it's my post he's referencing. That's a bit disconcerting, I feel responsible for trashing MongoDB all over the internet. At least my conscience is lighter because everything I wrote was true...
Yes, it was true that the 32bit version of mongodb that is limited to 2gb would lose your data if you injected more than 2gb in it, shame on mongodb...
Jesus, I can't believe people still defend this shit. I don't care if MongoDB can store ten jiggerbytes, it should give an error when you're trying to insert more than that. When the hell did corrupting your data become acceptable for a datastore?
Re: CouchDB Notice for 1.0.1 - Potential Data Loss
#8Earlier quoted context omitted.
Yes, it was true that the 32bit version of mongodb that is limited to 2gb would lose your data if you injected more than 2gb in it, shame on mongodb...
Jesus, I can't believe people still defend this shit. I don't care if MongoDB can store ten jiggerbytes, it should give an error when you're trying to insert more than that . When the hell did corrupting your data become acceptable for a datastore?
The 32bit version is available for convenience, nobody uses it in prod. You can't complain that a simple testing tool limited to 2gb can't store more than 2gb.
Re: CouchDB Notice for 1.0.1 - Potential Data Loss
#9Earlier quoted context omitted.
Jesus, I can't believe people still defend this shit. I don't care if MongoDB can store ten jiggerbytes, it should give an error when you're trying to insert more than that . When the hell did corrupting your data become acceptable for a datastore?
The 32bit version is available for convenience, nobody uses it in prod. You can't complain that a simple testing tool limited to 2gb can't store more than 2gb.
When did I complain it couldn't store more than 2 GB? I complained because it silently corrupted my data.
Re: CouchDB Notice for 1.0.1 - Potential Data Loss
#10Earlier quoted context omitted.
The 32bit version is available for convenience, nobody uses it in prod. You can't complain that a simple testing tool limited to 2gb can't store more than 2gb.
When did I complain it couldn't store more than 2 GB? I complained because it silently corrupted my data.
You used a dev version of a tool that is not meant to be ran in production or for any serious task and then complained it didn't work with your attempt. As this bug is not present in the real prod version of mongodb, it doesn't make sense to criticize mongodb for it. Also next time RTFM before using a tool you don't know much about.