In this lesson we're going to discuss the new plug-in interface for MySQL. Well it's relatively new, it came in, in version 5.1. It has been expanded somewhat and we have a lot more plug-ins now in version 5.5 but we're still not making total use of it. There are a number of different types of plug-ins that this interface allows for. The most prevalent one right at the moment are pluggable storage engines. In fact all the storage engines in version 5.5 are now plug-ins. So that's a good thing, that allows us then to introduce new storage engines if we need to as long as they're written properly as plug-ins to an existing server while it's running. So we can plug in a new storage engine and then store data in a new way if we need to. It's also designed to use full text parser engines. So this would allow us then to redefine how words are determined or to be able to set up full text indexing for other storage engines than just MyISAM which is the one that does it right now. So full text parser engine is another useful thing and that's actually the first thing that was mentioned in the manual but storage engines as plug-ins have just kind of taken off. We can also have information schema plug-ins. So we have a few of those in our system right now to in version 5.5. They came along with the InnoDB plug-in and we also have the performance schema out there which is another information schema like thing. We can have daemon plug-ins as well. Now what would that be? A daemon plug-in would be something that would launch from within the MySQL server, a background process and would be able to manage that. Now I can't come up with a good example of this for you right at the moment but imagine if you will some new process that we want to launch over on the side to be running for awhile, while our server is running. That's what a daemon plug-in would do. And ultimately they're going to allow us the ability to replace user defined functions which now has a totally separate interface with plug-in functions instead which should make things a lot easier to work with and should make things a lot more uniform as well. Now where are these things stored? A lot of people will say well the plug-ins are all stored in the plug-in table in the MySQL database. And they're partially true. We do have to have that plug-in table in the MySQL database so anybody upgrading from version 5.0 to 5.1 will need to run the update program that adds that table to the MySQL database so that then they can use the plug-in facility. However, the only thing that's stored in the plug-in table is the path to a plug-in. Because the plug-ins exist somewhere out there in the file system on the host machine where the server is running as a code file. Just like plug-ins for anything else, if you've ever worked with plug-ins for, oh I don't know Photoshop then you know that those files are stored in a separate directory and Photoshop knows where to look for those. Well in this case we can put them probably pretty much anywhere as long as we give the proper path to it knowing that storage engines are the most prevalent use of plug-ins now, that's all we're going to talk about, plug-ins for the moment. But we do have a little bit more to say about storage engines just for background information here, just for thoroughness. So the next lesson will be about storage engines.
| Course: | MySQL 5 Administration-Part 1 |
| Author: | David Swain |
| SKU: | 34307 |
| ISBN: | 978-1-61866-086-2 |
| Release Date: | 2012-12-31 |
| Duration: | 16 hrs / 171 lessons |
| Work Files: |
Yes |
| Captions: | No |
| Compatibility: |
Vista/XP/2000, OS X, Linux QuickTime 7, Flash 8 |