Answer:
1) Yes, Publisher relation should have a publisherID primary key.
2) NOT NULL and UNIQUE for the BookID, BranchID, CardNumber and name of the borrower in the Book, Book_Copies, Library_branch, and Borrower relations respectively. The DueDate field of the book_loan relation must be a time constraint. The BookID of the Book relation must be serial number for automatic addition and update of bookid across the database.
Explanation:
The Publisher relation should have primary key publisherID which should replace the publisherName in the Book relation to easily make a join query and attain a third-level database model.
Answer:
By presuming the question expect us to write a program to address the problem and the solution code written in Python is as follow:
- beer_name = input("Enter beer name: ")
- abv = int(input("Enter ABV value: "))
-
- if(abv > 10):
- label = "Very High"
- elif(abv >=6):
- label = "High"
- elif(abv >=3):
- label = "Average"
- else:
- label = "Low"
-
- print("Beer Name: " + beer_name)
- print("ABV value: " + str(abv))
- print(label)
Explanation:
Firstly, we can use input function to prompt user to input beer name and ABV value (Line 1 - 2).
Next, create if else if statements to check abv fallen into which range of value and then set a label accordingly (Line 4 -11). For example if abv is 4, the label will be set to "Average".
At last, print the information of beer that includes beer name, abv value and label (Line 13 - 15).
Answer: no why huh hmmmmmmm
Explanation:
5x+2y=3
Slope = -5.000/2.000 = -2.500
x-intercept = 3/5 = 0.60000
y-intercept = 3/2 = 1.50000
2x+3y=13
Slope = -1.333/2.000 = -0.667
x-intercept = 13/2 = 6.50000
y-intercept = 13/3 = 4.33333
I believe the answer is D)system area <span />
