Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a tabular representation of a relation called staff, I have been asked to complete a number of tasks like the degree and cardinality which is 5 and 3, but i have been asked why it is not meaningful to talk about the 2nd tuple in the relation and i have no idea why that would be the case.
*This is a practise exam, which came with no answers.
A tuple is to a relation as a row is to a table.
There is no notion of order in a relation (a relation is defined as an unordered set of tuples).
In a table (as you have displayed), order is an artifact of display – there is no concept of order in the relational model (although one could add the concept as an attribute of a tuple/row).
So there is no concept of the 1st, 2nd or 3rd tuple
Similarly, in a SQL RDBMS, order of returned rows is not guaranteed except where an
ORDER BYis specified.