Inside MySQL: Sakila Speaks Por arte de portada

Inside MySQL: Sakila Speaks

De: Oracle Corporation
Escúchala gratis

  • Resumen

  • The Inside MySQL, Sakila Speaks podcast is dedicated to all things MySQL. We bring you the latest news from the MySQL team, MySQL product updates, and inciteful interviews with members of the MySQL Community. Sit back and enjoy as your hosts, Fred Descamps and Scott Stroz, bring you the latest updates on your favorite open-source database.
    2024
    Más Menos
Episodios
  • Mastering MySQL Group Replication

    Mastering MySQL Group Replication
    May 28 2024
    Luis Soares, Senior Software Development Director and the "face" of all things MySQL replication, drops by to enlighten us about group replication and its different uses in the MySQL ecosystem.
    Más Menos
    14 m
  • MySQL Shell Does All The Things!

    MySQL Shell Does All The Things!
    May 7 2024
    For this episode, Fred and Scott are joined by Miguel Araujo, Senior Principal Software Engineer for MySQL Shell. Miguel outlines MySQL Shell's history and discusses its more popular and powerful features. The conversation winds down with us discussing our favorite features. --------------------------------------------------------- Episode Transcript: 00;00;09;13 - 00;00;30;16 Welcome to Inside MySQL: Sakila Speaks, a podcast dedicated to all things MySQL. We bring you the latest news from the MySQL team, MySQL product updates and insightful interviews with members of the MySQL community. Sit back and enjoy as your hosts bring you the latest updates on your favorite open-source database. Let's get started. 00;00;30;20 - 00;01;01;11 Hello and welcome to Sakila Speaks, the podcast dedicated to MySQL. I'm leFred and I'm Scott Stroz. I know today's guest for a long time already has had the chance to work with them on several solutions. Please welcome Miguel Araujo, Senior Principal software Engineer on the MySQL Shell Team. Miguel is the technical lead developer of the Admin API, core component of the HA and the replication solutions like the MySQL InnoDB Cluster MySQL InnoDB replica set and MYSQL InnoDB cluster set. 00;01;01;28 - 00;01;25;07 Welcome, Miguel. Hey guys. Thanks for inviting me to this podcast. So, Miguel, we want you to talk about MySQL Shell. Can you give us a high-altitude overview of what MySQL Shell is? Basically, what it is, who should be using it and why? So first and foremost, Shell is the command client for my SQL Server, right? 00;01;25;21 - 00;01;50;28 You can do with Shell what you could do with a classic MySQL client. So, you connect to a server to my SQL server and it can run queries on it using SQL. But Shell is much, much more than that. It's a... we like to call it a modern advanced command client for MySQL server, and maybe I should get a little quick history lesson about it. 00;01;50;28 - 00;02;27;00 So, Shell came out with... there was a purpose to build this new command client and this kick comes back to 2016. If I recall correctly, when the document store was being developed and implemented. And with MySQL Doc Strore we have created this new API to interact with it, the X-dev API, and this X-Dev API follow the common standards and this was implemented in JavaScript in Python, and for that we needed a new shell, a new command line client to interact with the server and speak. 00;02;27;10 - 00;03;05;16 This is new API and interact with the Doc Store. So, for that we create this shell with the with implementation of the X-Dev API exposed in JavaScript and Python. So Shell was born with a with this multi-language support so SQL classic and then JavaScript in Python and in the beginning with with the X-Dev API exposed to those two languages. But we also built it as a modern interface, so it has a customizable and reactive prompt. 00;03;05;29 - 00;03;32;21 It has auto-completion, syntax highlight. It has a built-in help system. So, it's built as the for example, we have in Linux bash or the Shell or on Shell or whatever or in Windows PowerShell and Shell can be seen as something like that. But for MySQL, so you started your shell, you can run commands in it, you can connect to instances and operate on them. 00;03;32;21 - 00;04;06;21 So, it has this interact interface and also a scripting interface because since you have support for those languages, for JavaScript Python and SQL you can write your own scripts and then you can execute them in in Shell. And a another general feature ... most known and, and useful are the APIs built in. So I was just mentioning the X-Dev API that was the first one. 00;04;07;07 - 00;04;37;05 And then we of we have introduced the Shell API and the utilities and then the Admin API and the so starting with the Shell API, for example, we have operating system utilities. You can create reports, you can create plugins. The utilities include things such as the upgrade checker that is a utility built in shell that you can use to verify whether your server is ready to be upgraded to the new version. 00;04;37;20 - 00;05;09;05 And if not, what needs to be done. You have things as dump and load to dump instances and load them. This is very fast. It's it's very loved by the community and the Admin API that is used to deploy MySQL architectures like Fred said in the beginning – InnoDB cluster states replica set and so on. And also Shell is extensible, can write plugins for it and that's something great. 00;05;09;05 - 00;05;35;10 And that's one of the things that makes it a modern client. Yeah, to be honest, I am a very fan of Shell. It replaced the old MySQL client for me, the classic one I always use Shell everywhere. And so recently during the MySQL Belgium days, who you are there, you were speaking also about Shell. Many people like Booking.com and Canonical guys. 00;05;35;18 - 00;05;58;14 They praised MySQL shell. They use ...
    Más Menos
    28 m
  • MySQL Goes LTS! (Stories From the Cloud)

    MySQL Goes LTS! (Stories From the Cloud)
    Apr 22 2024
    The MySQL Team has implemented a new versioning model that includes LTS. Geir Hoydalsvik, Senior Director of Software Development for MySQL stops by to give a primer on this new versioning model and breaks down the differences between the '8.0' releases and the 'Innovation' releases. ------------------------------------------------------- Episode Transcript: 00;00;09;13 - 00;00;31;20 Welcome to Inside MySQL: Sakila Speaks, a podcast dedicated to all things MySQL. We bring you the latest news from the MySQL team, MySQL product updates and insightful interviews with members of the MySQL community. Sit back and enjoy as your hosts bring you the latest updates on your favorite open-source database. Let's get started. 00;00;32;01 - 00;00;55;00 Hello and welcome to Sakila Speaks, the podcast dedicated to MySQL. Hi, I'm leFred and I'm Scott Stroz and I'm Geir Hoydalsvik. Yeah. Today our guest is Geir Hoydalsvik, software developer, director, responsible for MySQL development and maintenance of the MySQL database. This includes the following teams: server General, Runtime Optimizer, InnoDB, Server QA, and Sustaining. 00;00;55;04 - 00;01;19;15 Am I right? Yeah, that's correct. Geir, in April, the very first LTC version of MySQL will be released. Can you tell our listeners why this is significant? Yeah, that's the answer to kind of a customer and user request is to have stable releases that people can pick up security bug fixes, for example, without risk of having regressions by new feature and so on. 00;01;19;15 - 00;01;47;18 So, the long-term support release that we call LTS is actually stable for eight years, that people can buy support for this time period and essentially, they're guaranteed stability for a long time. Thank you. So between the LTS, so the major release, we will also release innovation releases. So, are those developments releases, or are there also production GA quality? 00;01;47;28 - 00;02;42;26 Thank you. A good question. They are also production quality. So, the current plans are that every second year we will release an LTS release and between two LTS test releases we will release, as you said, innovation releases every third month. So, there will be roughly eight of those between two LTS and they are production quality so people can get support or will get support with having these releases in production and this will be for people that are okay with more frequent changes and, and are willing to spend the energy of upgrading and so on between these and perhaps also take into account that releases features can go away deprecate old deprecated features can be 00;02;42;26 - 00;03;08;28 removed in innovation releases while they're never removed in LTS releases. So that's what people need to keep in check out, but they're absolutely useful and they will be supported. So as a follow up to that, what's the difference in the numbering between the LTS releases and the innovation releases? When it comes to version numbers, there is kind of a transition now between eight oh and eight four. 00;03;08;28 - 00;03;46;16 So, the first LTS release will be called 8.4 and that becomes in April. Then the main the LTS releases will be called 8.4.1, 8.4.2, 8.4.3, 8.4.4, 8.4.5 and up. So, the maintenance releases of all that LTS will be called like that. Then at the same time we will start producing innovation releases for a 9 series. So, there will be and I know 9.0, 9.1, 9.2 and so on up to 9.7 that is planned to be the next LTS release. 00;03;46;16 - 00;04;13;24 And I think in the future it will be probably more like 10 will be the next series and then 11, or at least that's how we think about it today. So, you can say that 8.4 is a little bit an exception there. That transition into a 9.0, 10.0, 11.0 and type of numbering. And then the second number will be the innovation release number essentially. 00;04;13;24 - 00;04;46;00 So, the main is the first one, the LTS number, and the second is the innovation, roughly speaking. So, it's our understanding that all of the MySQL products will follow the same release model, but not the connectors. Can you talk about that? That's that's correct. So, all the server-side products will follow the same LTS model. While on the connectors side, you are recommended to use the latest connectors that will then support all previous releases. 00;04;46;00 - 00;05;22;28 So. So when you use the latest, you can use the current release and everything older kind of thing. So that's how it works. And yeah, it's a pragmatic choice that we feel is what users want us to do is actually. So, when we see what will and what will happen with the LTS, something that I noticed is and for me maybe the most significant change is compared to what we had with the MySQL 8.0 is that in the LTS lifecycle, the downgrades and clone between different minor version will be supported, isn't it? 00;05;22;29 - 00;05;50;19 Yes, that is correct. So, this is a change from 8.0 train...
    Más Menos
    9 m
Economía
Más Menos

Lo que los oyentes dicen sobre Inside MySQL: Sakila Speaks

Calificaciones medias de los clientes

Reseñas - Selecciona las pestañas a continuación para cambiar el origen de las reseñas.

Reseñas de Audible.com

Opiniones de Amazon
No hay comentarios disponibles