Choose the appropriate contraint type for what is descibed: Field, Table, Foreign Key, Front End
You are working for FedEx. They have asked you to work on a database for all things packages.
This database has a few different tables in it and also works in and around a few different
applications. You will see some of them noted in a question. When you look at packages, there's
a lot of constraints out there we have to deal with to make sure all of our information is correct
and we don't get any bad errors that harm our trucks or fail to send the package from some sort
of error in the label information.
Density of the package is within an appropriate limit for our truck (note that density involves all
four of length, width, height, and weight that you are entering)
Email address is a string (a data type)
Email address contains an @ sign somewhere in the middle, and a "." after the @ sign, separated
by at least one character and not immediately at the end, verified by sending a quick email to the
address to confirm it
Width is less than or equal to Length Only one package goes to a destination, which means the
combination of all things having to do with the address (which is multiple fields) must be distinct
from all other addresses in that table.
Length, Width, Height, and Weight are all >0. Again, consider this from the perspective of any
one of these.
Length, Width, Height, and Weight all determined to be NOT NULL. Consider this from the
perspective of any one of these.
Determining the package can fit on the truck, managed by a Tetris like application on your
computer Type of package (media, standard, live, biohazard), stored as a hardcoded list in the
table's definition
The packages getting loaded onto this truck (the Shipment table includes both the truck and the
package), but the package info is stored somewhere else in another table
ZIP Code (placed through a GIS application to match the address properly)
ZIP Code has exactly five characters
Nothing about the sender and the recipient is the same (except possibly the city, state, ZIP)
Declaring the packageID as primary key
State, chosen from a list stored in another table.
Beginners Guide to TikTok for Search - Rachel Pearson - We are Tilt __ Bright...
Choose the appropriate contraint type for what is descibed Field, T.pdf
1. Choose the appropriate contraint type for what is descibed: Field, Table, Foreign Key, Front End
You are working for FedEx. They have asked you to work on a database for all things packages.
This database has a few different tables in it and also works in and around a few different
applications. You will see some of them noted in a question. When you look at packages, there's
a lot of constraints out there we have to deal with to make sure all of our information is correct
and we don't get any bad errors that harm our trucks or fail to send the package from some sort
of error in the label information.
Density of the package is within an appropriate limit for our truck (note that density involves all
four of length, width, height, and weight that you are entering)
Email address is a string (a data type)
Email address contains an @ sign somewhere in the middle, and a "." after the @ sign, separated
by at least one character and not immediately at the end, verified by sending a quick email to the
address to confirm it
Width is less than or equal to Length Only one package goes to a destination, which means the
combination of all things having to do with the address (which is multiple fields) must be distinct
from all other addresses in that table.
Length, Width, Height, and Weight are all >0. Again, consider this from the perspective of any
one of these.
Length, Width, Height, and Weight all determined to be NOT NULL. Consider this from the
perspective of any one of these.
Determining the package can fit on the truck, managed by a Tetris like application on your
computer Type of package (media, standard, live, biohazard), stored as a hardcoded list in the
table's definition
The packages getting loaded onto this truck (the Shipment table includes both the truck and the
package), but the package info is stored somewhere else in another table
ZIP Code (placed through a GIS application to match the address properly)
ZIP Code has exactly five characters
Nothing about the sender and the recipient is the same (except possibly the city, state, ZIP)
Declaring the packageID as primary key
State, chosen from a list stored in another table
