All right.
So it's your turn to put some of this into practice with a single exercise.
It should be pretty quick.
All you need to do is define a single table.
So here are the demands.
Well, the man sounds a little strong.
Here are the requirements.
Define an employee's table.
So let's say we're a company trying to manage some employees.
We'll definitely need more data than this to actually make it operational.
But for now, this is all we need.
Seven different fields.
Seven columns.
ID last name, first name and middle name.
And then age and current status.
And actually, I can't count.
This is six.
So ID is relatively self-explanatory.
It should be a number.
I'm not telling you the data types, but you should know at this point what they are.
So a number that automatically increments it's mandatory.
So it can't be left off.
And it's a primary key.
Last name and first name are both text, which is in the data type.
Again, you need to use the actual term and then neither of them can be left blank either.
They're mandatory, but middle name.
While it's also text, it isn't mandatory because not everyone has a middle name so we can leave that
blank.
Then we've got age which is numeric and it is mandatory, can be blank.
And finally, current status, which is essentially like their employment status, if they're employed
or if they're fired and it should be mandatory.
So it can't be null.
But if no status is provided, when something is inserted, it should default to employed.
So we'll have to statuses employed and terminated or fired or something, I guess terminated.
It's more professional and so it should just default to current status is employed if nothing is provided
when it's inserted.
So go ahead and define this table.
Type it out.
Try running it to make sure it works and then try inserting some data as well to make sure that it works.
If you want a solution, have it in the next video.