https://github.com/fernandesotero/fcc-periodic-table-db
Solution for Perioc Table Data Base challange at @freecodecamp
https://github.com/fernandesotero/fcc-periodic-table-db
bash-script dbms git postgresql
Last synced: 3 months ago
JSON representation
Solution for Perioc Table Data Base challange at @freecodecamp
- Host: GitHub
- URL: https://github.com/fernandesotero/fcc-periodic-table-db
- Owner: fernandesotero
- Created: 2025-02-23T21:40:23.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2025-02-24T14:54:45.000Z (over 1 year ago)
- Last Synced: 2025-02-24T15:45:53.609Z (over 1 year ago)
- Topics: bash-script, dbms, git, postgresql
- Language: Shell
- Homepage: https://www.freecodecamp.org/learn/relational-database/build-a-periodic-table-database-project/build-a-periodic-table-database
- Size: 3.91 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Periodic Table Data Base
A Database that has information about some chemical elements.
# Tests Cases from FreeCodeCamp
- You should rename the weight column to atomic_mass
- You should rename the melting_point column to melting_point_celsius and the boiling_point column to boiling_point_celsius
- Your melting_point_celsius and boiling_point_celsius columns should not accept null values
- You should add the UNIQUE constraint to the symbol and name columns from the elements table
- Your symbol and name columns should have the NOT NULL constraint
- You should set the atomic_number column from the properties table as a foreign key that references the column of the same name in the elements table
- You should create a types table that will store the three types of elements
- Your types table should have a type_id column that is an integer and the primary key
- Your types table should have a type column that's a VARCHAR and cannot be null. It will store the different types from the type column in the properties table
- You should add three rows to your types table whose values are the three different types from the properties table
- Your properties table should have a type_id foreign key column that references the type_id column from the types table. It should be an INT with the NOT NULL constraint
- Each row in your properties table should have a type_id value that links to the correct type from the types table
- You should capitalize the first letter of all the symbol values in the elements table. Be careful to only capitalize the letter and not change any others
- You should remove all the trailing zeros after the decimals from each row of the atomic_mass column. You may need to adjust a data type to DECIMAL for this. The final values they should be are in the atomic_mass.txt file
- You should add the element with atomic number 9 to your database. Its name is Fluorine, symbol is F, mass is 18.998, melting point is -220, boiling point is -188.1, and it's a nonmetal
- You should add the element with atomic number 10 to your database. Its name is Neon, symbol is Ne, mass is 20.18, melting point is -248.6, boiling point is -246.1, and it's a nonmetal
- You should create a periodic_table folder in the project folder and turn it into a git repository with git init
- Your repository should have a main branch with all your commits
- Your periodic_table repo should have at least five commits
- You should create an element.sh file in your repo folder for the program I want you to make
- Your script (.sh) file should have executable permissions
- If you run ./element.sh, it should output only Please provide an element as an argument. and finish running.
- If you run ./element.sh 1, ./element.sh H, or ./element.sh Hydrogen, it should output only The 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 an atomic_number, symbol, or name in the database, the only output should be I 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:, or test:
- You should delete the non existent element, whose atomic_number is 1000, from the two tables
- Your properties table should not have a type 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