Pep has a broad experience in several database platforms, but in recent years he has focused on MySQL. His work abides by the motto of Mission Control at NASA: “Tough and competent”. Tough means you are accountable for what you do or fail to do, it means compromise and responsibility. Competent means that you take nothing for granted and you must never be found short in knowledge and skills. This is how Pep feels and lives database management. He is also interested in applying Lean culture to his job and enjoys living in Barcelona with his kids and his partner.
Presentation: Temporal tables: uncut and uncensored
MariaDB 10.3 introduced System Versioned Tables, and 10.4 will extend this feature to support Application Based Versioning. Combining both System and Application versioning we can support Bi-temporal data. Temporal data as defined in the SQL2011 standard, provides basic support for compliance and related business requirements and reduces application development complexity and cost by making this feature part of the core database. Some commercial databases have included support to temporal data, as this is considered a critical feature for some financial and accounting applications. In this talk we will cover the basics of temporal data and how this is implemented in MariaDB Contents: Temporal tables: adding the time dimension to databases.-Temporal data concepts and problems System versioned-Application versioned-System Versioned tables support in MariaDB 10.3 Basic operations-Innodb features-Replication-Performance considerations Application Based Versioning support in MariaDB 10.4-Basic operations-Replication-Performance considerations Disclaimer: MariaDB 10.4 has not been released GA yet, so some of the features described in the talk could change, even before the talk takes place 😉