I belive their were answer chocies to this question am i right
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:
depends
Explanation:
it lies with the entire firm and its ability to utilize or process the information in the most efficient way.
Answer:
Answered below
Explanation:
With the evolution and growth of technology, and as we are increasingly having our everyday lives dependent on technology, there arise problems that shouldn't be ignored.
Security of people's personal data and information is of paramount importance. Access to personal information and the sale of these information to companies without the owner's permission is a breach of privacy and one of the challenges we face today.
With the growth of data, there are newer threats and attacks on software security systems to steal these data and therefore there's a need for everyday assessment and improvement in security of data.
<span>or by following directions on screen </span>
