Create a Bash script to get information about chemical elements from a periodic table database.
Project made as part of the FreeCodeCamp Relational Databases Beta Certificate course
Connected to the periodic database provided by FreeCodeCamp, fixed mistakes and added appropriate constraints and extra chemical elements information.
Created a Bash script (version controlled with git) that accepts an argument in the form of an atomic number, symbol, or name of an element and outputs some information about the given element.
View: elements.sh
- Connect to the database
periodic_table
which is already available. Get a little familiar with the existing tables, columns, and rows. - Read the instructions below and complete user stories to finish the project.
- There are some mistakes in the database that need to be fixed or changed. See the user stories below for what to change.
- Make a small bash program. The code needs to be version controlled with
git
, so you will need to turn the suggested folder into a git repository.
- Make a script that accepts an argument in the form of an 'atomic number', 'symbol', or 'name' of an element and outputs some information about the given element.
- Rename the
weight
column toatomic_mass
- Rename the
melting_point
column tomelting_point_celsius
and theboiling_point
column toboiling_point_celsius
- The
melting_point_celsius
andboiling_point_celsius
columns should not accept null values - Add the
UNIQUE
constraint to thesymbol
andname
columns from theelements
table - The
symbol
andname
columns should have theNOT NULL
constraint - Set the
atomic_number
column from theproperties
table as a foreign key that references the column of the same name in theelements
table - Create a
types
table that will store the three types of elements - The
types
table should have atype_id
column that is an integer and the primary key - The
types
table should have atype
column that's aVARCHAR
and cannot benull
. It will store the different types from thetype
column in theproperties
table - Add three rows to your
types
table whose values are the three different types from theproperties
table - The
properties
table should have atype_id
foreign key column that references thetype_id
column from thetypes
table. It should be anINT
with theNOT NULL
constraint - Each row in your
properties
table should have atype_id
value that links to the correct type from thetypes
table - Capitalize the first letter of all the
symbol
values in theelements
table. Be careful to only capitalize the letter and not change any others - Remove all the trailing zeros after the decimals from each row of the
atomic_mass
column. You may need to adjust a data type toDECIMAL
for this. Be careful not to change the value - Add the element with atomic number
9
to your database. Its name isFluorine
, symbol isF
, mass is18.998
, melting point is-220
, boiling point is-188.1
, and it's anonmetal
- Add the element with atomic number
10
to your database. Its name isNeon
, symbol isNe
, mass is20.18
, melting point is-248.6
, boiling point is-246.1
, and it's anonmetal
- Create a
periodic_table
folder in theproject
folder and turn it into a git repository withgit init
- Your repository should have a
main
branch with all your commits - The
periodic_table
repo should have at least five commits - Create an
element.sh
file in your repo folder for the program I want you to make - Script (
.sh
) file should have executable permissions - If you run
./element.sh
, it should outputPlease provide an element as an argument.
and finish running. - If you run
./element.sh 1
,./element.sh H
, or./element.sh Hydrogen
, it should outputThe element with atomic number 1 is Hydrogen (H). It's a nonmetal, with a mass of 1.008 amu. Hydrogen has a melting point of -259.1 celsius and a boiling point of -252.9 celsius.
- If you run
./element.sh
script with another element as input, you should get the same output but with information associated with the given element. - If the argument input to your
element.sh
script doesn't exist as anatomic_number
,symbol
, orname
in the database, the output should beI could not find that element in the database.
- The message for the first commit in your repo should be
Initial commit
- The rest of the commit messages should start with
fix:
,feat:
,refactor:
,chore:
, ortest:
- You should delete the non existent element, whose
atomic_number
is1000
, from the two tables - Your
properties
table should not have atype
column - You should finish your project while on the main branch. Your working tree should be clean and you should not have any uncommitted changes