Some months ago I started work on a way to test random, valid SQL in CockroachDB. This is important to expose unintended behavior in our server.
We recently improved our distributed SQL performance by implementing column families in CockroachDB. Column families are commonly found in NoSQL databases.
This blog post outlines how fuzz testing uncovered a Schrodinbug in CockroachDB, how Go was partly to blame, and how we addressed it using strong typing.
The good news is that CockroachDB’s JOIN seems to work, as in, “it returns correct results.” However, this is just our first, unoptimimized implementation.
We have added a new feature: time-travel queries. To our knowledge, we are the first database to have implemented the them.
Adopting SQL had an unexpected consequence; it forced us to dabble in language design. In this post, we detail our approach to SQL typing in CockroachDB.
CockroachDB's support for SQL means access to a variety of data frameworks and tools. Today, we'll build a simple application in Python using SQLAlchemy...
CockroachDB contributor Paul Steffensen (aka uptimeDBA) has analyzed CockroachDB's handling of NULL values as compared to other SQL implementations.
CockroachDB is pretty easy to deploy. However, there is still one wrinkle in the fabric, and that's our use of network ports.
In this post, we will go over some of the factors involved in choosing the best index to use for running a certain query.