When indexing JSON documents in PostgreSQL, you can add indexes for the access patterns just like with relational table columns. We will walk through an example of this using the Pokémon GO Pokédex as a dataset, utilizing YugabyteDB, a distributed SQL database compatible with PostgreSQL.
Welcome to this week’s tips and tricks blog where we recap some distributed SQL questions from around the Internet. We’ll also review upcoming events, new documentation, and blogs that have been published since the last post. Got questions? Make sure to ask them on our YugabyteDB Slack channel, Forum, GitHub, or Stackoverflow. Ok, let’s dive right in:
When should I use JSON vs JSONB data types?
Welcome to another post in our ongoing series that highlights new features from the latest 1.1 release announced last week. Today we are going to look at document data modeling using the native JSON data type available in YugabyteDB’s Cassandra compatible YCQL API. Note that this data type is specific to YugabyteDB and is not part of the standard Cassandra Query Language (CQL).
With YugabyteDB’s native JSON support,