What a perfect time to rename it to something reasonable
huh, seems like a fine, memorable name to me.
What to Expect in CockroachDB 1.0
11–20 of 47 posts
Re: What to Expect in CockroachDB 1.0
#12What a perfect time to rename it to something reasonable
ElegantDB - Named after C. elegans
In reference to radioresistance: While an LD50 has been reported for wild type C. elegans individuals, an upper lethal limit has not been established, rather "nearly all animals were alive with no indication of excess lethality up to 800 Gy, the highest dose... measured."
Re: What to Expect in CockroachDB 1.0
#13The company decided to remove direct access to their transactional key-value store and force interactions through the SQL layer. From this comment in the FAQ, it looks like the overhead for some mutations is small: https://www.cockroachlabs.com/docs/frequently-asked-question... Do range queries on a simple table also translate to underlying key-value range queries with minimal overhead?
Yes. (I work there too)
Re: What to Expect in CockroachDB 1.0
#14I am a database newbie, what are it's pros and cons over postgres?
Re: What to Expect in CockroachDB 1.0
#15What a perfect time to rename it to something reasonable
Agreed. Atrocious name. Same with Mozilla's "Rust". Great language, terrible name.
Re: What to Expect in CockroachDB 1.0
#16CockroachDB supports the PostgreSQL wire protocol, but does it support JSONB and GIN indexes?
Re: What to Expect in CockroachDB 1.0
#17CockroachDB supports the PostgreSQL wire protocol, but does it support JSONB and GIN indexes?
Not yet. On the roadmap though.
Re: What to Expect in CockroachDB 1.0
#18Re: What to Expect in CockroachDB 1.0
#19Any newer Jepsen test since this one: https://jepsen.io/analyses/cockroachdb-beta-20160829 Also, how's the performance nowadays?
The tests that Aphyr describes are ran regularly, to prevent regressions.
Re: What to Expect in CockroachDB 1.0
#20What a perfect time to rename it to something reasonable
Just about every news item on HN related to cockroachdb has had this comment up at the top. We get it. (I do NOT work for the company.) Some people don't like the name. I'm sure the company has heard it over and over. Yet they haven't changed it.
At some point, these people who constantly protest the name should realize they've been heard and let the discussion focus on something other than their pet peeve that has nothing to do with the underlying tech. Yes, we realize you have a problem with the name. We realized it a dozen news items ago. But since this is HackerNews, you'd think other aspects -- distributed transactions and the approach they took, the fact that this is in Go (!) and the benchmarks on it, the single executable that incorporates the C++ RocksDB embedded leveldb, etc, etc -- would take top billing.