# data[].attributes.body
Today, our project has been completed.  Thanks

# data[].attributes.body
Today we have appointment 18.00pm.

# data[].attributes.body
Today we help each other to clean data in excel again . Do the report chapter 1&2 . Record the video about create database and tables untill 3.30 pm to 11.40 pm

# data[].attributes.headline
We adjust SQL code on Phpmyadmin,ER diagram will be like this. 

# data[].attributes.subject
We adjust SQL code on Phpmyadmin,ER diagram will be like this. 

# data[].attributes.headline
To day we have appointment at 15.30 pm. to do about report

# data[].attributes.subject
To day we have appointment at 15.30 pm. to do about report

# data[].attributes.body
(everytime when we working we use discord to disscus)

# data[].attributes.body
to do for chapter2

# data[].attributes.body
6 april   7.30-11.00  p.m.
We have worked on the report chapter 1.  And manage data in excel

# data[].attributes.body
Today we appointments 16.00

# data[].attributes.body
To day we appointments at 18.00pm

# data[].attributes.headline
And We have some quetion about vendor table.

# data[].attributes.subject
And We have some quetion about vendor table.

# data[].attributes.body
today we appointment 8.00 p.m.

# data[].attributes.body
Today we appointments to do project 7.00 p.m.

# data[].attributes.body
Please re-watch video lectures to the case from your slides Database Normalization on page 39. The case is very similar. You don't need Customers in your project.

# data[].attributes.body
Picture 4 is closer to truth, so work on it.
But...
Let's take an example! Your Vendor table: You have two concepts in one table. One concept is about Vendor and another one is product. Split Vendor table into smaller tables: If you have Vendor table each row must tell a story about a particular Vendor. Cost doesn't tell anything about Vendor it tells something about the product that Vendor sells.
Each row should have different Vendor. So , you will have only 3 vendors in the table. And the primary key will be Vendor name. You don't need foreign Key here
Now, can you guess where should be the Cost? In what table? Right, SKU table1
In this SKU table every row must have different SKU and that row should tell a story related to SKU only. Remember in SKU table your primary key will be SKU id number and IMPORTANT --> the primary key MUST never ever ever eveeeeeer repeat in one table. So remembering this lets try to figure out we need to know about this SKU.
1) color, size, style ? hmm maybe..most likely , yup
2) cost? sure
3) now here comes the Vendor attribute: should we include it. If we include it than in the future we should be able to link those two tables. That means Vendor will be inlcuded as Foreign Key
3) anything else? Department? yup. But again we need to have a separate table which tell the story about the department just like we Had our Vendor table.
So if we include department  it must be included as foreign key

In the same way try to split the Store table that you have into simple several tables that tell a story only about its Primary key. Your Store table in Picture 4 is waaaay too general and irrelevant. Try to do it and post the result here Tomorrow!
I am waiting ......

# data[].attributes.headline
 Data model V.1     we help each other to do this diagram then we have a little confused and not sure. If we get wrong please explain for us. 

# data[].attributes.subject
 Data model V.1     we help each other to do this diagram then we have a little confused and not sure. If we get wrong please explain for us. 

# data[].attributes.body
We analyze problems from data.

# data[].attributes.body
And talking in Line group

# data[].attributes.body
We meeting in Discord

# data[].attributes.body
Next ,We appointments to do project at 8.30 p.m.

# data[].attributes.body
Today  we appointments to do project at 1.50 p.m.

# data[].attributes.body
Member group
Chayanin Ukrathikan 6031209027
Natnicha Kaisanga 6031209040
Pattarin Angkasupon 6031209093
Suphuk Chucherd 6031209193
Atittaya Boontun 6031209196

# data[].attributes.body
Today will make an appointment for work at 8pm.