In the second part of this blog series on PostgreSQL and YSQL date-time data types, the focus shifts to representing durations, or how long things last. Assuming the reader has read the first part and downloaded the companion code kit, this post explores the relevant data types, including interval, timestamp difference, and other related functions.
This is the first of a two-part blog post series that deals with the basic business of representing moments using time, date, and timestamp data types. YugabyteDB’s YSQL subsystem provides a similar experience to PostgreSQL, so the topic may still be enlightening for some YSQL users.
PostgreSQL has eaten the world. And so Yugabyte set out to build the most Postgres-compatible, scalable, and resilient database. YugabyteDB is not only wire compatible with PostgreSQL, it is code compatible by reusing the upper half of PostgreSQL. Thanks to this compatibility, YugabyteDB can connect to the vast majority of database tools that integrate with Postgres.
In a previous blog post, Yugabyte Developer Advocate Franck Pachot showed how to connect YugabyteDB in Arctype.
…
Yugabyte brings best-in-class performance, scalability, and availability to YugabyteDB, a fully PostgreSQL-compatible SQL database. Because YugabyteDB’s architecture uses PostgreSQL at the SQL layer, we get a long-tail of PostgreSQL compatibility for free. But implementing savepoints requires deeper integration into YugabyteDB’s distributed persistence and transaction layers.
In this blog post, we’ll discuss why you should care about savepoints. We’ll also examine how we built savepoints into YugabyteDB’s distributed transaction layer,
…
At Yugabyte, we are committed to complete PostgreSQL compatibility. Similar to PostgreSQL, YugabyteDB supports the following three container column types. These three data types are extremely useful in various cases:
Each data type’s utility is severely limited without an efficient way to index them.
…
In this blog post, you’ll learn how to implement a timer for multi-statement operations using SQL with YugabyteDB or PostgreSQL. These tools are commonly used for various tasks, but their native timing feature only times individual SQL statements and doesn’t support end-to-end timing or output to spool files.
YugabyteDB is PostgreSQL compatible. It uses the same protocol and SQL layer as PostgreSQL. This makes YugabyteDB compatible with a majority of database tools, because PostgreSQL is the most popular open source database on the planet. Here is an example with Arctype, a user-friendly collaborative SQL client to query and visualize data.
1. I went to https://arctype.com/ and downloaded the client for Windows.
2.
…
YugabyteDB is an open source, high-performance distributed SQL database built on a scalable and fault-tolerant design inspired by Google Spanner. YugabyteDB uses its own special distributed document store called DocDB. But it provides SQL and stored procedure functionality by re-using the “upper half” of the standard PostgreSQL source code. This is explained in the two part blog post “Distributed PostgreSQL on a Google Spanner Architecture”: (1) Storage Layer;
…
YugabyteDB is an open source, high-performance distributed SQL database built on a scalable and fault-tolerant design inspired by Google Spanner. YugabyteDB uses its own special distributed document store called DocDB. But it provides SQL and stored procedure functionality by re-using the “upper half” of the standard PostgreSQL source code. This is explained in the two part blog post “Distributed PostgreSQL on a Google Spanner Architecture”: (1) Storage Layer;
…
Yesterday we had almost 200 folks show up for the latest “YugabyteDB Fundamentals and Certification” training session. We had a lot of questions during the session and weren’t able to get to them all! In this blog I have compiled the majority of them and provided answers in a simple Q&A format.
Missed yesterday’s training? You can catch our next training session, “YugabyteDB YSQL Development and Certification and Training” on Feb 25 by registering here.
…
