creating these classes requires equipment and service.
Is that cost money?
If you appreciate this education, please think about going to Eli the computer guy dot com and offering a one time or monthly recurring donation.
So today's video we're gonna have a brief introduction to be my sequel databases.
So the question may be asking is what is a database and why is it important?
So all a database is is is a type of software that you install it onto a server that is able to store data for you.
So it makes it very easy to input in store data, and it makes it very easy to be able to retrieve data when you need it.
So databases are used as what is called the back end for many of the Web applications and even normal applications that you use every day s.
So let's say you have some type of invoicing software, so you use QuickBooks or use fresh books.
You something like that, right?
So you have you have customers, you have technicians or sales people.
You have different parts and inventory.
You have a whole bunch of different types of data that have to be stored.
Basically, that data is then stored onto some type of database.
So all be clear.
All the database does is it stores the data.
Then what you do is you build a front end, and so the front end is whatever application you're using to actually be able to interact with the data.
That front end is able to then communicate back with the database and be able to pull out the data that it needs or push data into the database when you need to store.
So let's say you're adding a new customer, right?
So you're adding a new customer, so there's a new customer form.
You type in the first name you type in the last name.
You take all that information into the form when you click, submit that information.
That data is then taken, and it's safe to the database.
If you then in the future, I need to do a report and see who all of your customers are.
You click the button for the report, your software.
Your application will then go to the database.
It will get all the information for those different customers and then the applications will print out all of that data for you, for you to be able to read as a report.
So one of the important things to remember whenever you're dealing with databases, whether it's in my sequel database or any other time of database, is all the database does.
Is it stores data for you?
That is it.
You're going to need some other front and application for you to actually be able to access and interact with the data and something that anybody would consider a user friendly fashion.
This is one of the problems a lot of people run into because many times people's first introduction to databases with something called Microsoft Access so make yourself access is a database application.
Basically, it's a personal kind of personal small business, a database application, But with that, you get the front end, you get the database component, you get the coding, you get the intelligence you get.
Everything is one package.
So when people download or they install my sequel for the first time, they're expecting, they're like, Well, how do I How do I interact with my new database?
How do I do anything?
Because as as always with a lot of things in the real world.
Once you install the application, all you get is a little blinking cursor, and you don't get any friend fancy front end.
So the important thing to understand is you are able to interact with the database from the basic command line.
But to actually create a piece of software, something that is useful to the end user, you're going to have to have a front and application built that will then communicate back with that database.
So that's the basic idea of what databases are.
But some of his clients will explain a little bit more about why you're gonna be using the my sequel database and a little bit about what you need to start using my secret database.
Now one of the first questions you may be asking is, Why are we learning about my sequel database?
Isn't my sequel some old, archaic, nasty, grotesque type of database?
Why aren't we using something like Mongo D.
B or no sequel database or something like that?
Why deal with one of these old old technologies?
Well, because the reality is in the I t world many times we deal with what are called legacy technologies.
Basically, what legacy technologies are is when we go out, we build out these massive infrastructures in order to build on a massive infrastructure.
You need a lot of different components.
You need a lot of different products to make that infrastructure work.
And so one of things that that's been out for a couple of decades now is in my sequel database.
And so my sequel has been built into the ah lot of the solutions that we're using.
And so one of the reasons that we need to learn about my sequel is because it's already being used and that is already being used.
More people are going to continue to use it.
And so, theoretically, even if there is a better solution out there, it's It's an inertia thing you gotta understand in the I T world is this.
There's an idea.
There's an idea of the I T world you know, every year it's new and it's changed and we forget about the past.
Let let me tell you the real I to world when you some really feel products, why do we use them really old products because, you know, they worked pretty well.
They worked pretty well.
We've already built our infrastructure based off of it, and so we're going to keep on going.
So one of the big reasons why you need to know about my Siegel even if you don't use it in the future for building applications or building out your infrastructure is because it is simply already used significantly.
So if you look at work word presses is built off of nice equal droop.
A was built off of my sequel.
So many off the shelf products are basically basically Web applications that you will download and host on your own.
They use my sequel as the back end.
So understanding my sequel is a very important thing, if for no other reason, simply because it is used so widely, you will run into it in the real world.
And so you might as well understand how it works.
Now, the next question answer is how to get your hands on my sequel.
So you decided to use my sequel as the back in front of her application you're gonna be creating, So how do you actually get your hands on it?
and get it up and running well.
The easiest way to get my stable up and running and simply to go to a share hosting provider by their lowest price share hosting plan and get me my sequel database that they give you.
So if you go to go in attica dot com host gator dot com Any of these Web these shared hosting plans, even there at least expensive one will generally give you at least one my sequel database with up to a gig of storage.
And so basically, you can simply connect to their my secret out of a servers you connect to your my sequel database, and then you're able to put down into that database and pull down out of the database.
And essentially, as far as you coding your application, it looks more or less identical to if you were actually running your own database server yourself.
So I will say, You know, I tell people on the times, instead of building your own server, a lot of a lot of new people out there they always want to build their own servers and, you know, start learning that way.
One of things that I argue is you go with a simple share hosting plan, then you don't have to worry about stupid ass firewalls you don't have to worry about.
I S P is blocking random ports.
You don't have to worry about CPU fans failing.
You don't have to worry that you turned on u F W and you didn't realize it, which is a Lennox firewall, right?
You don't have to worry about a lot of issues.
If you go with a simple, shared hosting plan, they will give you the database that will give you the connection credentials.
And then you're simply able to connect your application to that database.
And then you can learn from there when the big problems that I see is people try to build their own servers on when they build their own servers and especially their new Not only they're learning how to run my sequel server, but they're also learning Lennox and they're also learning hardware, and they're also learning that working so that can cause you a lot of problems.
So I would argue for a lot of people, the best bet is simply to go get a share of hosting plan use the my sequel database that they provide for you and then build your applications from that.
When you feel comfortable doing that, then you can go and build your own database server.
Beyond that, there is infrastructure is a service, so so eight of us offers a my sequel solution.
There's a lot of other Cloud based My sequel solutions out there were.
Basically you get the full size enterprise class, my sequel database.
You simply connect your application to it and they deal with high availability.
They deal with all the fancy things, that kind of thing then.
Beyond that, if you actually do want to install my sequel onto your own server, you can go basically, go to Oracle's website on Oracle's website.
There's a community edition of my sequel, and you can download and install that.
And again, it's simply a piece of software.
And so because it simply a piece of software, it has been ported.
You can install it.
There's versions for Lennox.
There's versions for Windows, and there's versions for Mac operating system.
Now the next thing that I got to talk about is where we get into a little bit of the weeds a little bit of the history of my sequel because there's also another option for you called Maria de Be So Maria di B is basically it is a fork of my sequel.
The reason Maria Di B is very important is because, as you heard before, I talk about, you can go to Oracle's Web site and download my sequel, and that gets a lot of people nervous.
The reason being is my sequel used to be its own company.
So way back when I actually took training from my sequel itself and my sequel was its own company.
It was a company dedicated to open source, and basically the way that it made its money was by selling training and bite by selling.
Consulting service is well, then, a number of years ago, a company called Sun Microsystems with floundering and it still had a lot of money.
It still had a lot of money, but it wasn't really sure where it's business was going, so it decided to go out and start buying a lot of open source projects.
So a open office it bought my sequel.
It bought a lot of the open source projects of the time, the idea being they will consult up.
They date them into Sun Microsystems, and then Sun Microsystems would become.
There's this major, big, basically open source corporation and everything.
What, everything be good.
The problem is, it didn't really work out too well for them.
They were bleeding money before they purchased all the open source companies, and they're bleeding money after they purchased the open source companies.
And so what happens when your company is bleeding money?
Basically, another big company comes in and buys you out.
The problem for Sun Microsystems.
Or I guess the problem for the larger community is the company that decided to come in and buy out Sun Microsystems was or a coal.
Now it's kind of funny oracles, one of those companies that slides under the radar because Oracle is a business to business company.
You don't hear about it a lot, so you hear a lot about Microsoft.
You know, you hear about how horrible Microsoft's business practices are.
You're about how horrible Amazon or Google or Apple's business practices are.
The weird thing is you never hear about horrible like normal people don't talk a lot about Oracle Well, I think is in the realize the world, the real enterprise world Oracle has a pretty crap reputation.
They they do some curious that let's just say that you some curious things and so oracles, mainly a database company.
So they create the Oracle database.
And so the issue is when they mop Sun Microsystems.
And then once they own Sun Microsystems they owned by sequel.
They own so many of these other open source projects.
You had a lot of people that were very nervous about what the future of products such as my sequel will be.
And so, since my Sequels open source of the time, what they did is they forked my sequel off and they continue development under Maria de Be So you will hear about Maria de Be every once in a while.
Basically, basically, Maria Davey should be what's called a drop in replacement for my seat.
With a drop in replacement Means is, basically, you should simply be a bill.
You should be able to connect whatever software that you have that's most connect to my sequel database to Meridia be and everything should work fine.
So basically, if you code, an application and PHP that communicates with my sequel.
You should be a bit connected to Maria de B and have no issues.
You should be able to export data all your information from my sequel imported into Maria de B, and you should get You should have no problems.
So whenever you hear about things such as Maria de Be, understand these Air Force of that original my sequel, the idea being that people want to keep that completely open source because they are legitimately worried about what?
What Oracle will do with these different open source projects so that let's go over the computer so I can just give you a little bit of an overview of where you can actually get your hands on my sequel and some of the things that you need to be thinking about when you actually want to go out and deploy my sequel into your environment.
So the first and I would argue, the best place to go For most people that air, initially learning my sequel is again just to go to some someplace like Go Daddy o, our host gator or whatever else.
If you come down here you can see and have their different little hosting plans.
They have got a little more expensive in the years, but okay for so for them, $6 a month or $8 a month, all the way to $20 a month.
They give you all of these different things.
But if you come down, you take a look at what all plans include one of things that all the plans include is one gig database.
Store it for my sequel, Lennox s.
Oh, this is good.
So again, if you want to start building small applications, if you want to figure out how my sequel works, that type of thing, what you can do is you can simply pay that, you know, $6 a month.
Then you're able to actually create a database on Go Daddy.
And then you can go from there.
You don't have that.
Then you're not worried about firewalls.
You're not worried about CPU fans failing?
You're not worried about all that stupid crap.
You can focus on learning my sequel, and you would focus on learning the whatever code that you're learning or to connect to my sequel, and that's it.
Past that, though, if you do want to go larger, you have decided to build out some kind of large application, and you want my sequel as the back end.
Something to really think about is companies such as Scale Grid.
So have my sequel is a service fully managed my secret with high availability, performance optimization and disaster recovery on the best of my secret service for cloud, blah, blah, blah.
And so again, this is gonna be an important thing to be thinking about when you're going to be deploying databases into your infrastructure.
Not only do you have to worry about making sure that your code can connected it at a base, can send out a database to retrieve data from the database, but what happens in a disaster situation?
What happens if a tornado comes through and wipes out your your server room?
What happens if Daddy gets corrupted?
What happens in your database is sitting on a corrupted hard drive and data within the database that thing becomes corrupted, right?
These were some of the things that you really have to think about so realistically, just off loading this onto some kind of infrastructure of the service.
Some companies, like a scale grid, might be a good idea for you.
Now, if you really do you want to install my sequel yourselves?
You're like No, Eli, no.
I wanna put my sequel onto my own servers.
I will deal the disaster recovery and all that kind of stuff.
Basically, you can come and again.
You go to my sequel dot com products community and you can come here.
You can see the different additions for my sequel, and the one that you're going to be looking for is the my sequel, Community Edition.
And so, with my sequel, Community Edition, you can see all of this fancy stuff that you're able to get within my sequel communication.
The important thing to realize about this is that this is open source and this is free.
So basically there is no licensing on this.
You can create a little application in your home.
You can scale that out through the global application, and there's going to be no additional cost for you.
But do you realize if you want to use any give other fancy tools that my sequel has offer, you may then actually have to pay for it.
So again, this is where you know we talk about things like open source, and I get really irritated when people talk about open source because they always they always say, like it's free and you can view it like people have this idea of open source.
That's just not That's just simply not really just not simply not how it is.
So my sequel is open source, so if you want to use the free version, you can use the Mice Equal Community Edition.
But to get some of the other features and functionality that you may need, you may need to pay for one of the other additions, and we talk about paying for the other additions were talking about some real money here gets on my sequel.
Standard Edition is US $2000.
My sequel, Enterprise Edition, is $5000.
My sequel clusters is for clustering is $10,000.
So again, this is just one of those things to keep in your mind is, as as you build out your infrastructure As your company gets larger and larger, you may need certain features and functionality that's not provided in something like the community addition, and all of a sudden you go from what you consider a free license to literally an annual subscription.
That's an annual subscription of 10 that $1000 a year.
So that's gonna be one of those things to think about.
But again, if you're just playing with it, if you're just learning how to deal with this stuff on again, even even in business applications or reasonable business applications, the community issue will be completely fine.
Just realized that if you do have to go up in the world, it may cost you a lot of money.
Then, beyond that again, you go over and take a look at Maria de Be Again Goodbye Oracle, right?
That's a big thing.
A lot of people hate Oracle.
There's a lot of horrible haters out there, and so they're like, Hey, you, hey, an oracle Come over to Maria D.
Maria Di B is basically supposed to be a drop in replacement for my sequel, but one of things that I won't will say, even with Maria de Be Again it's open source and one of the versions is free diversions.
This free right eso again.
They have a community edition, so their community edition has a lot of features and functionality, but one of problems you can run into again.
Even this is though this is open.
Source is if you notice under the community edition, you get replication and clustering, but you don't get automatic.
Limiting right There's actually a lot of functionality here that you don't get with the community edition.
So if you need some of this stuff again, like automatic, fail over its huge automatic fail over.
If you're running your own database, servers is a massive thing, and so you may have to have to pay in order to get access to that.
So again, this is one of those things you really need to be thinking about.
A lot of people have this idea that if you're using our purchasing or I guess you're using open source software that for some reason that it's always free when in reality it can get very expensive very quickly.
If you need a particular feature set that's not included with the community version but basically, these are the ways you can get access to my sequel again.
You can simply go to my sequel, download the version that you want.
You can go to Maria de be if you want again.
I would argue.
Probably the best way to start is simply to go to go Daddy or host Gator and use the service is that they offer there.
So now that you know how to download and install my sequel, one of the next questions and you're gonna have is okay.
How do I actually do anything with this, Right.
So again, one of the big problems in the Lenox world in the real anti administration world is basically you install a product, you and sell a piece of software, and then after it's installed, you get a little blinking cursor, and then you're like, Well, now what do I do?
So if you install my sequel or Maria de be on the Lennox Oh, our Windows or Mac or whatever else.
Basically, once it's installed, you just get a little blinking cursor, and then you have to figure out what to do next.
Now, the first way that you can interact with your my sequel database is through and that command line.
There's something called sequel statements.
So sequel SQL is called structure query language.
And at that ling little blinking cursor, you can actually type in commands in sequel to Do Things suck as create tables to create, to create records to create different things within the database.
So if you just want to sit there and basically hand a type everything out, you can in fact do that so you can get all the functionality from your my single database literally by using the command line.
But as with most things, just cause you can do it doesn't necessarily mean that's how you really want to be interacting with the database.
That could be a real pain.
Interact with the database that way.
So what a lot of people do.
Well, you'll most likely be used.
And if you use something like share hosting plan as you will use a front and it's called PHP, my admin.
So what PHP my admin does is it gives you a nice graphical user interface that shows you all your tables.
It gives you all your commands.
You can click this rename this.
Do all that kind of stuff that you're used to basically with a graphical user environment and makes life a lot easier.
S O that is a web based applications.
So basically, what you do, you install that onto a lamp server.
So a lamp server is a Lennox Apache, my sequel, PHP server.
And so you have my sequel installed on your server You then install with called PHP my admin.
And with that, you're able to simply open up a Web browser.
You're able to access PHP my admin, and then once we're able to access it, you're able to log in.
And then again, you can see your databases.
You can see your tables.
You can see your records, you can import, you can export.
You can do everything thing in a graphical fashion, eh?
So that's the way that you'll most likely be dealing with my sequel for basic like like preventive maintenance tasks and basic different types of tasks.
The final way that you're gonna be interacting with your database is simply through whatever code that you create in order to interact with your database.
So if you're using PHP or possibly Ruby on rails or some other coding language.
Basically, you can code so that your script is able to access that database and then do whatever it is that you want.
So its able to create records is able to read from records, is able to modify records.
Basically, with that code, you can have the full functionality of being able to administer the database.
You just have to determine basically what you want that code to actually be able to D'oh.
So when you're sitting there trying to figure out how you're gonna be interacting with my sequel again, yes, you could do the command line.
That is a way that is away.
I would not recommend it for most people, really, What you want to do is you want to figure out how to install PHP.
Once you've installed PHP, my admin, then you get access to it again from a Web browser.
Then you can go in.
You can actually take a look at the structure of your mind sequel database.
You can see again tables that rose the records, all of those different types of things, and then you'll be able to interact with your my sequel databases that way.
So now let's talk about what?
A relational databases.
So when you hear about my sequel or Maria de B or other different types of databases, you may hear that they're called relational databases.
So what does this actually mean?
And why is this important to you?
Well, one of the big things is whenever going be designing any kind of infrastructure and be designing any kind of application.
One of things you have to think about is how are you going toe logically segment out different components of whatever you're trying to build.
So what happens with a relational database is you have tables.
The tables ours within the database, you have different tables and they store like types of information.
So let's say you have a customer's table.
So the customer's table, where the customer i d.
I don't have the customer name.
It'll have the customer address.
It'll have a customer email, customer phone number.
Ah, whole bunch of different other information.
Then you may have a parts table so the parts table will have a parts I d.
It will have the name of the part.
May have the skew for the part about the description for the part of the price.
For the part, I have the wait for the part of your shipping parts, that type of thing.
You may have a vendor's table so the vendor's table will have a vendor I D.
And I'll have the vendor named the vendor address basically who your contact people information are and so on and so forth.
So we're talking about a relation all database.
What we dio is we separate the different types of data that's going be stored into their own logical units.
So this is the customer's table.
This is the vendor's table.
This is the parts table.
Then you may have something like an invoice table.
So it's really cool with relational database is, since you have those I d.
You have a party.
You're the customer, I d.
Then when you have something such as an invoice, instead of having to rewrite all the information in an invoice table, you can simply a reference the customer i d.
And the part I d that you're talking about for the invoices, you can say invoice.
One is, you know, for customer.
I D to buying Part three and you know, whatever else information there, And so that's what we're talking about with a relation.
All database is basically how these tables relate to each other.
So let's go over to my little white board for a second to kind of explain this a little better, and I think it would make sense when it when I scribble it out.
Okay, so here's a representation of three different tables.
So at the top we have the invoices table.
So basically, this is for the invoices that are being created for the business.
Then we have a customer's table, and then we have a part table.
So basically, we take a look at the end of voice table.
What we're talking about with Relational database is we can sit here and take a look at the invoice I D.
So it basically every invoice that's created has its own unique I D.
And so for invoice 0001 you can see it's for customer I d.
0002 So basically this relates down to customer i d.
And so when we say custom righty 00 to what we mean is customers to sue Thompson at customer address for 32 High Street, and their email address is su at gmail dot com.
So instead of having to print all of this out in this one table, I am simply able to reference that customer I d.
And from that I'm able to pull the information.
So basically, when I'm when I'm writing out the full code, then again So we look for this and voice.
And so for invoice, one customer 002 is purchasing part I d.
So if I take a look at part I t Sierra 02 I have a part table party t 002 is here.
That is a sprocket.
The description of Sprocket is it's a good sprocket and it costs $3.
So this is a apart price here, right?
So instead of having to write all of that out, I can simply a reference the part i d there.
And then finally at the end for the invoice status, right?
So, basically, for the envoy status, what is the envoy status?
So for envoys 001 of the invoices shipped for envoy 002 The invoices refund it.
And for a 003 of the invoice is in process, right?
So you can have these different tables.
So basically, if I wanted to create a report based off of invoices, I could simply then find that the basically pull from the different invoice I d.
S wait goes through.
It pulls from the invoice idea, goes the customer.
I d pulls the information that I want.
The custom righty then pulls the information I want from the part I d pulls any other information within this particular record.
And then I am able to print that out.
Same for 002 Same for 003 So again, for invoice I D and voice I d.
002 we have customer I d three.
So that's come down here.
So we're referencing Tim Dean at 9 87 Market Street.
Tim at hotmail dot com He purchase an item part item 001001 is a caw ge is a hefty caw ge and it costs a dollar.
And for whatever reason, this particular invoice has been re funded.
So This is what we're talking about with a relation A LL database.
So you have these different tables.
These different tables are then related to each other, and you use that with these different identify IRS.
So that's the basic idea what we're talking about with relational database.
So the final thing that I want to talk about is basically to give you a brief overview of sequel or structured queria language.
So structure query language is the language that we will be using in order to communicate with your my sequel database.
So whether you're using PHP or Ruby on rails or another coding language, basically, what will happen is you'll you'll write out your script and that other coding language and then, at some point, basically, what you'll do is you'll use sequel to then either put data ended Anatomy's or pull data out of the database.
So whether you're typing out the sequel statements at the command line or you're using PHP to input the sequel statements into my sequel, you're always going to be interacting with the my sequel database using structured query language.
It's a relatively easy language to understand, and so I just want to give you a brief overview of it.
So with that, let's go over the computer.
I have a little Web page brought up from a particular site that I think is useful for these types of tutorials.
And so with that, I'll kind of give you a big, brief demonstration of how sequel works.
So here we are at W three schools dot com.
So if you have not been to W three schools dot com, this is a very useful site to go to, at least for basic and introductory information on How did you deal with different Web programming languages on They have a little Siri's here on sequel Select statements.
Figure this was easier than spitting up a server to try to show you how how all this works.
But the cool part is you can come here and they actually give you ways.
Thio play around and deal with demonstrations s.
So I think this is a very useful tool.
So with this, I just want to show you like basic select statements, So a select statement allows you to go into a database and pull data out.
So if you want to read data from a database.
So what we have here is we have the select commands were saying select all from the table.
So from, and then whatever your table name is, so this is going to select all the data from whatever table.
So if this is the parts table would select all from the parts table.
It was the customer table.
It's like all from the customer's table and basically would print it out for you on a screen.
Go down here.
They have a basically basically demonstration database that they created.
So this database it has columns for customer I D.
Customer name and contact, name, address, city, postal code and country.
And you can see they have different records.
The custom ready 1234 and five.
Alfred Anna around the horn, blah, blah contact, name, address, city, postal, code, country and so forth.
So we can see down.
Here is where they have a sequel statement.
And so for this particular database, they say, select the customer name.
So they want to see the customer name and they want to see the city.
And I want to see the city from the table customers and so This is the table customers here, right?
So you go try it ourselves.
We can see that.
So select customer, customer name, comma city from customers If we run sequel.
Basically what this did is it pulled out the customer name and pulled out the city and then it printed everything out.
I could then do.
Let's a comma country on that.
If I run sequel now we can see you get the customer name the city and the country.
I can also then do something called Order Bye and then I couldn't say customer name.
So basically, if I want to sort by a particular column So for this customer name, I could do something called Order by.
I can then run sequel and then we can see it is now ordered by the customer in a.
Or I could order by, Let's say, order by city.
If I wanted to see you see what people are in the same city by order by city.
Then we can see it is now ordered is now sorted by the city.
So this just basically gives you a little bit of an idea of what sequel looks like again.
This is gonna be a sequel.
Siri's so I'm going to be teaching you a hell of a lot more about sequel.
You will understand how sequel sequel statements work better and future classes.
But when you hear about C Hole and just want you to have this idea of this is how it works, Basically, this is the language that you're using to communicate with your My sequel database did t be able to put data end and a B of a polling data out.
And this is this is just an overview of how it looks and basically what I say this w three tutorials is a great sight to go through.
So just a brief introduction to the my sequel database again in future videos, I'm going to show you how to install my sequel.
I'm gonna show you how to connect to it.
Using programming languages such as PHP.
I want to show you how to use PHP.
My ad men.
I'm going to show you a lot of other things, but I think this is just a brief overview to give you an idea of what you're getting into, and we start talking about my sequel so again.
My sequel is only one type of database software that is out there again.
A database is simply a type of server software that allows you to easily store and retrieve data again.
Generally, we're talking about storing and retrieving data.
We're talking about things like CR M Solution.
So customer relationship management solutions.
You have a bunch of customers have a bunch of sales people.
So a database is a very good place to store that type of data.
One of the reasons I want to show you folks how to use my sequel and other databases going into future is I like little I ot projects, especially with these Little aren't.
We knows, right?
So these are Arduino microcontrollers.
And one of the cool things for these Arduino microcontrollers is they have full WiFi T c p I P four stacks on them so these little guys can actually connect to a wider, normal WiFi network.
And so they're able to pull data in so that you can put temperature sensors on these.
You put light sensors on these motion, since there's all kinds of different sensors, right?
But the thing is, you can put sensors on them, But what happens if you want to be able to store whatever?
Whatever it is, they're they're readings are.
So let's say every hour you want to know what the temperature is in a facility so on and so forth.
So basically using my sequel database, what Weaken Dio is we can weaken, build out these little devices, these little micro controllers, we can have them communicate with a server, and then you can have the server than store the records that these little micro controllers air providing into the database.
And then once it's in the database, you can run reports you can look and see what trend lines are.
You can do all of that kind of thing.
So databases and my sequel databases are very important, and they really are very useful in the modern world.
Now, the reason that we're again we're gonna be using my sequel is its legacy.
I know a lot of new people.
A lot of new guys hate it when I say things like we're gonna use it because his legacy.
But it's true, right?
So many products we use in the real world.
We're using him because we've always used my sequel has been around a really long time.
A lot of Web based software is built off of my sequel, so even for your projects and one in the future, even for your project going in future, if you designed not to continue using my sequel, that's fine.
But you should have a least a reasonable understanding of what it is and how it works right again, like with programming languages or anything else, You're not married to it.
Just because he learned my sequel doesn't mean you can't learn a different database, right?
You can learn my sequel, realize why it's either good or bad, and if you don't like it, you think can then go learn something else.
But you go and learn something else with the knowledge you front that you've already gained from being able to play around with my sequel.
Now, if again, if you do go out and you do want to deploy my sequel, you want to start playing with it.
I would recommend going to share hosting plan again go Daddy, host Gator, Whatever.
The cheapest option is out there again.
My sequel is an old technology.
You don't have to get the latest and greatest hosting plan to be able to use my sequel.
The nice thing about using a share hosting plan again is you don't have to worry about CPU fans you don't have to worry about.
Firewalls don't have to worry about the last stupid stuff.
Is there a couple of bucks a month?
But then you don't have to worry about troubleshooting.
If you do want to deploy your own server again, basically, you can either go to my sequel dot com or, if you're using Lennox and simply use pseudo you know, halfpipe and get installed.
You can simply pull it from a repositories, and you can install it onto your You're certain the one thing that I will warn you again, even though my sequel is open.
The whole question of what does open source actually mean so you can use the my that you can use the community version of my sequel that is open source, and that is free.
As far as I understand.
Read the license yourselves far as I understand that's free, basically for any application.
But one of one of problems you're gonna run into right is you know, there's just somebody's nice again, like audit their fail overs.
And there's just some of these really nice features that you would really like to use.
And one of the issues that you're going to run into again with No Seat is with my sequel is Basically the free version does 99% of all the stuff that you need in order to get that, you know that one piece of functionality that one feature that's not included in the community edition it may literally cost you 2 to $10,000 a year.
So do be careful that again.
The same thing is through with Maria de Be So Maria Di B is the is the fork fork of my sequel.
Basically, when Oracle bought some, Microsystems bought my sequel lot people concerned about that.
And so that's where Maria de Be got forked off again.
Even with Maria D'You hear about, that's like, Oh wow, So this is an open source project in order to keep you know, my sequel, you know, free and open for everybody to use.
And again you go to the Maria DBS website.
You can see that there's there's the non subscription edition, and then there's a subscription edition now again for most people.
Most people don't need to pay for the subscription genuinely.
But if you're going to start putting my sequel into a production environment, having fail over having some of these other things is a very useful thing to have and you start find out.
Oh, it's gonna actually cost me a couple of bucks to do that.
So that's one of those things just to keep in mind again.
As Faras Relational databases is concerned, You have something called a scheme.
Um, we'll talk about all of this a lot more going to the future with the schema you have.
You have tables, and those tables have columns.
And so basically what it is is you group like types of information into tables, so all your parts will be in the parts table.
All your customers will be in the customer's table.
All your invoices will be in the invoice table.
Why is a relational database is because then you can create relations between the different table.
So again for invoices, you have the invoice, I d.
And you simply relate you.
You have a customer I d.
That relates to the customer table.
You're the part I d.
That relates to the part table, and then you have any other it if it additional information, they're.
So instead of having to print out all of the data into all these different tables, you simply have basically these pointers to records in other tables.
That's what we're talking about with the relational databases, and then finally show you how the sequel statements were a little bit again.
The big thing to remember with sequel statements is this is simply the language that you're going to be using in order to communicate with your my sequel databases.
Whether using PHP, whether your hand typing it in, it's going to be the same sequel statements.
And so you're simply going to have to learn this language.
And then once you've learned that language, then then you figure out how how you plan to interact with the database is gonna be PHP.
Is it gonna be ruby on rails?
It's gonna be some other programming language, so you write all the code and the other programming language, and they basically just add the my sequel in order to do the connections to the database.
I'll show you all that kind of stuff in the future.
So anyways, that was the introduction to my sequel again.
This is very interesting when you understand how how useful data bases can be, especially in the world of coyote devices and love the other stuff that you could do, it really opens just a whole world of things that you could d'oh that you probably didn't think about before.
So so, yeah, look, I look forward to doing that the rest of the series on with that as always, I enjoy doing this video and 40 on the next one.