Now, you'll create a database from scratch.

Create a database representing LinkedIn from scratch, as by writing a set of CREATE TABLE statements in a linkedin.sql file. The implementation details are up to you, though you should minimally ensure that your database meets the platform$$s specification and that it can represent the given sample data.

Users

The heart of LinkedIn$$s platform is its people. Your database should be able to represent the following information about LinkedIn$$s users:

Their first and last name

Their username

Their password. No need to worry about hashing passwords.

Schools and Universities

LinkedIn also allows for official school or university accounts, such as that for HackYourFuture Belgium, so alumni $($i$.$e$.,$ those who$$ve attended$)$ can identify their affiliation. Ensure that LinkedIn$$s database can store the following information about each school:

The name of the school

The type of school $($e$.$g$.,$Elementary School$,$Middle School$,$High School$,$Lower School$,$Upper School$,$College$,$University$,$ etc.$)$

The school$$s location

The year in which the school was founded

Companies

LinkedIn allows companies to create their own pages, like the one for HackYourFuture Belgium, so employees can identify their past or current employment with the company. Ensure that LinkedIn$$s database can store the following information for each company:

The name of the company

The company$$s industry $($e$.$g$.,$Education$,$Technology$,$Finance$,$ etc.$)$

The company$$s location

Connections

And finally, the essence of LinkedIn is its ability to facilitate connections between people. Ensure LinkedIn$$s database can support each of the following connections.

Connections with People:

LinkedIn$$s database should be able to represent mutual $($reciprocal$,$ two$-$way$)$ connections between users. No need to worry about one$-$way connections, such as user A $$following$$ user B without user B $$following$$ user A$.$ Connections with Schools

A user should be able to create an affiliation with a given school. And similarly, that school should be able to find its alumni. Additionally, allow a user to define:

The start date of their affiliation $($i$.$e$.,$ when they started to attend the school$)$

The end date of their affiliation $($i$.$e$.,$ when they graduated$),$ if applicable

The type of degree earned$/$pursued $($e$.$g$.,$BA$,$MA$,$PhD$,$ etc.$)$

Connections with Companies:

A user should be able to create an affiliation with a given company. A company should be able to find its current and past employees.

Additionally, allow a user to define:

The start date of their affiliation $($i$.$e$.,$ the date they began work with the company$)$

The end date of their affiliation $($i$.$e$.,$ when left the company$),$ if applicable

The title they held while affiliated with the company

Your database should be able to represent...

A user, Alan Garber, whose username is $$alan$$ and password is $$password$.$

A user, Reid Hoffman whose username is $$reid$$ and password is $$password$.$

A school, Harvard University, which is a university located in Cambridge, Massachusetts, founded in $1636.$

A company, LinkedIn, which is a technology company headquartered in Sunnyvale, California.

Alan Garber$$s undergraduate education at Harvard, pursuing a BA from September $1$st$,1973$ to June $1$st$,1976.$

Reid Hoffman$$s employment with LinkedIn as its CEO and Chairman, from January $1$st$,2003$ to February $1$st$,2007.$