They are versatile because they can be used for all sorts of tasks. They can also do many of the same tasks in different ways. They are diligent because they will do a task thoroughly until it is finished.
They work at a constant speed to do the task. Unlike a human, they will not slow down or get bored or start making mistakes that they were not doing earlier. So once they are programmed correctly to do a task, they will do it diligently.
Packet loss is typically resolved by time-outs and retries. For applications where a duplicate operation doesn't matter this is acceptable.
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:
#include <bits/stdc++.h>
using namespace std;
int main() {
string in;//string in for taking input...
cout<<"Do you want to continue ?"<<endl;
getline(cin,in);//taking input from the user...
if(in=="y"||in=="Y"||in=="yes"||in=="OK"||in=="Why not?")//conditions..
cout<<"OK"<<endl;
else if(in=="No")
cout<<"terminating"<<endl;
else
cout<<"Bad input"<<endl;
return 0;
}
Explanation:
I have taken a string in.
Then taking input from user.
Checking the conditions using if else if ladder.
I believe the answer would be B taking b2 and b3 together and then subtracting b4 from the total number
