Non-First Normal Form natural join operation












0















I have 2 tables in non-first normal form:



enter image description here



What would be the result of the NATURAL JOIN operation of these two table?










share|improve this question




















  • 1





    Please read & act on How to Ask, hits googling 'stackexchange homework' & the downvote arrow mouseover text. Quote the definition(s) you are using. Show/justify your work/reasonin following them. The first place you are stuck explain about why. PS Please use text, not images/links, for text (including code, tables & ERDs). Use a link/image only for convenience to supplement text and/or for what cannot be given in text. And never give a diagram without a legend/key. Make your post self-contained.

    – philipxy
    Nov 23 '18 at 19:44








  • 1





    What relations are those grids pictures of? You don't have an attribute name topping your columns & you don't have a single value for an attribute in a row. Suggest you rewrite them so you do. We can guess that the third column in each has attribute name X--is that right? We can guess that the value for an X attribute is the obvious relation made from the array of values & attributes C & D--is that right? (You are confusing something about attribute names & types.) Quote your textbook's definitions of "relation" & "natural join" (etc), give the relation values clearly & show work using them.

    – philipxy
    Nov 23 '18 at 19:53








  • 1





    PS If you made proper headings that were sets/lists of attribute names and just replaced the attribute values by xN, what would your answer be? PS If you were given those grids, how were you told to interpret them as relations? PS What does this have to do with your tag object-relational-model? PS "1NF" has no single meaning.

    – philipxy
    Nov 23 '18 at 20:00


















0















I have 2 tables in non-first normal form:



enter image description here



What would be the result of the NATURAL JOIN operation of these two table?










share|improve this question




















  • 1





    Please read & act on How to Ask, hits googling 'stackexchange homework' & the downvote arrow mouseover text. Quote the definition(s) you are using. Show/justify your work/reasonin following them. The first place you are stuck explain about why. PS Please use text, not images/links, for text (including code, tables & ERDs). Use a link/image only for convenience to supplement text and/or for what cannot be given in text. And never give a diagram without a legend/key. Make your post self-contained.

    – philipxy
    Nov 23 '18 at 19:44








  • 1





    What relations are those grids pictures of? You don't have an attribute name topping your columns & you don't have a single value for an attribute in a row. Suggest you rewrite them so you do. We can guess that the third column in each has attribute name X--is that right? We can guess that the value for an X attribute is the obvious relation made from the array of values & attributes C & D--is that right? (You are confusing something about attribute names & types.) Quote your textbook's definitions of "relation" & "natural join" (etc), give the relation values clearly & show work using them.

    – philipxy
    Nov 23 '18 at 19:53








  • 1





    PS If you made proper headings that were sets/lists of attribute names and just replaced the attribute values by xN, what would your answer be? PS If you were given those grids, how were you told to interpret them as relations? PS What does this have to do with your tag object-relational-model? PS "1NF" has no single meaning.

    – philipxy
    Nov 23 '18 at 20:00
















0












0








0








I have 2 tables in non-first normal form:



enter image description here



What would be the result of the NATURAL JOIN operation of these two table?










share|improve this question
















I have 2 tables in non-first normal form:



enter image description here



What would be the result of the NATURAL JOIN operation of these two table?







database relational-database natural-join






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 23 '18 at 21:23









nvogel

20.9k12962




20.9k12962










asked Nov 23 '18 at 13:49









noobcodernoobcoder

498




498








  • 1





    Please read & act on How to Ask, hits googling 'stackexchange homework' & the downvote arrow mouseover text. Quote the definition(s) you are using. Show/justify your work/reasonin following them. The first place you are stuck explain about why. PS Please use text, not images/links, for text (including code, tables & ERDs). Use a link/image only for convenience to supplement text and/or for what cannot be given in text. And never give a diagram without a legend/key. Make your post self-contained.

    – philipxy
    Nov 23 '18 at 19:44








  • 1





    What relations are those grids pictures of? You don't have an attribute name topping your columns & you don't have a single value for an attribute in a row. Suggest you rewrite them so you do. We can guess that the third column in each has attribute name X--is that right? We can guess that the value for an X attribute is the obvious relation made from the array of values & attributes C & D--is that right? (You are confusing something about attribute names & types.) Quote your textbook's definitions of "relation" & "natural join" (etc), give the relation values clearly & show work using them.

    – philipxy
    Nov 23 '18 at 19:53








  • 1





    PS If you made proper headings that were sets/lists of attribute names and just replaced the attribute values by xN, what would your answer be? PS If you were given those grids, how were you told to interpret them as relations? PS What does this have to do with your tag object-relational-model? PS "1NF" has no single meaning.

    – philipxy
    Nov 23 '18 at 20:00
















  • 1





    Please read & act on How to Ask, hits googling 'stackexchange homework' & the downvote arrow mouseover text. Quote the definition(s) you are using. Show/justify your work/reasonin following them. The first place you are stuck explain about why. PS Please use text, not images/links, for text (including code, tables & ERDs). Use a link/image only for convenience to supplement text and/or for what cannot be given in text. And never give a diagram without a legend/key. Make your post self-contained.

    – philipxy
    Nov 23 '18 at 19:44








  • 1





    What relations are those grids pictures of? You don't have an attribute name topping your columns & you don't have a single value for an attribute in a row. Suggest you rewrite them so you do. We can guess that the third column in each has attribute name X--is that right? We can guess that the value for an X attribute is the obvious relation made from the array of values & attributes C & D--is that right? (You are confusing something about attribute names & types.) Quote your textbook's definitions of "relation" & "natural join" (etc), give the relation values clearly & show work using them.

    – philipxy
    Nov 23 '18 at 19:53








  • 1





    PS If you made proper headings that were sets/lists of attribute names and just replaced the attribute values by xN, what would your answer be? PS If you were given those grids, how were you told to interpret them as relations? PS What does this have to do with your tag object-relational-model? PS "1NF" has no single meaning.

    – philipxy
    Nov 23 '18 at 20:00










1




1





Please read & act on How to Ask, hits googling 'stackexchange homework' & the downvote arrow mouseover text. Quote the definition(s) you are using. Show/justify your work/reasonin following them. The first place you are stuck explain about why. PS Please use text, not images/links, for text (including code, tables & ERDs). Use a link/image only for convenience to supplement text and/or for what cannot be given in text. And never give a diagram without a legend/key. Make your post self-contained.

– philipxy
Nov 23 '18 at 19:44







Please read & act on How to Ask, hits googling 'stackexchange homework' & the downvote arrow mouseover text. Quote the definition(s) you are using. Show/justify your work/reasonin following them. The first place you are stuck explain about why. PS Please use text, not images/links, for text (including code, tables & ERDs). Use a link/image only for convenience to supplement text and/or for what cannot be given in text. And never give a diagram without a legend/key. Make your post self-contained.

– philipxy
Nov 23 '18 at 19:44






1




1





What relations are those grids pictures of? You don't have an attribute name topping your columns & you don't have a single value for an attribute in a row. Suggest you rewrite them so you do. We can guess that the third column in each has attribute name X--is that right? We can guess that the value for an X attribute is the obvious relation made from the array of values & attributes C & D--is that right? (You are confusing something about attribute names & types.) Quote your textbook's definitions of "relation" & "natural join" (etc), give the relation values clearly & show work using them.

– philipxy
Nov 23 '18 at 19:53







What relations are those grids pictures of? You don't have an attribute name topping your columns & you don't have a single value for an attribute in a row. Suggest you rewrite them so you do. We can guess that the third column in each has attribute name X--is that right? We can guess that the value for an X attribute is the obvious relation made from the array of values & attributes C & D--is that right? (You are confusing something about attribute names & types.) Quote your textbook's definitions of "relation" & "natural join" (etc), give the relation values clearly & show work using them.

– philipxy
Nov 23 '18 at 19:53






1




1





PS If you made proper headings that were sets/lists of attribute names and just replaced the attribute values by xN, what would your answer be? PS If you were given those grids, how were you told to interpret them as relations? PS What does this have to do with your tag object-relational-model? PS "1NF" has no single meaning.

– philipxy
Nov 23 '18 at 20:00







PS If you made proper headings that were sets/lists of attribute names and just replaced the attribute values by xN, what would your answer be? PS If you were given those grids, how were you told to interpret them as relations? PS What does this have to do with your tag object-relational-model? PS "1NF" has no single meaning.

– philipxy
Nov 23 '18 at 20:00














1 Answer
1






active

oldest

votes


















1














It is not exactly clear what your picture is supposed to represent. I'm going to assume that R1 is a relation with three attributes, A,B and X; R2 is a relation with three attributes, E,B and X.



The natural join would be a join where the values in B and X are equal in both R1 and R2. What type of attribute is X? If X is a relation-valued attribute and the columns labelled C and D represent the tuples in X then it seems that the relation values are different in each case. (X in R1 and X in R2 happen to have some of the same tuple values in common but the values of relation X are different in each case).



So the result of the natural join would be an empty relation with a heading of A,B,E,X but with zero tuples.






share|improve this answer


























  • Your picture is apt to confuse because it includes some sort of type info in column 3 of the heading when it doesn't for the others. If you're using some convention with a special layout for relation-valued attributes, you should say so. Even if that's maybe what the asker is consciously doing (in headings & values).

    – philipxy
    Nov 23 '18 at 20:47













Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53447928%2fnon-first-normal-form-natural-join-operation%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














It is not exactly clear what your picture is supposed to represent. I'm going to assume that R1 is a relation with three attributes, A,B and X; R2 is a relation with three attributes, E,B and X.



The natural join would be a join where the values in B and X are equal in both R1 and R2. What type of attribute is X? If X is a relation-valued attribute and the columns labelled C and D represent the tuples in X then it seems that the relation values are different in each case. (X in R1 and X in R2 happen to have some of the same tuple values in common but the values of relation X are different in each case).



So the result of the natural join would be an empty relation with a heading of A,B,E,X but with zero tuples.






share|improve this answer


























  • Your picture is apt to confuse because it includes some sort of type info in column 3 of the heading when it doesn't for the others. If you're using some convention with a special layout for relation-valued attributes, you should say so. Even if that's maybe what the asker is consciously doing (in headings & values).

    – philipxy
    Nov 23 '18 at 20:47


















1














It is not exactly clear what your picture is supposed to represent. I'm going to assume that R1 is a relation with three attributes, A,B and X; R2 is a relation with three attributes, E,B and X.



The natural join would be a join where the values in B and X are equal in both R1 and R2. What type of attribute is X? If X is a relation-valued attribute and the columns labelled C and D represent the tuples in X then it seems that the relation values are different in each case. (X in R1 and X in R2 happen to have some of the same tuple values in common but the values of relation X are different in each case).



So the result of the natural join would be an empty relation with a heading of A,B,E,X but with zero tuples.






share|improve this answer


























  • Your picture is apt to confuse because it includes some sort of type info in column 3 of the heading when it doesn't for the others. If you're using some convention with a special layout for relation-valued attributes, you should say so. Even if that's maybe what the asker is consciously doing (in headings & values).

    – philipxy
    Nov 23 '18 at 20:47
















1












1








1







It is not exactly clear what your picture is supposed to represent. I'm going to assume that R1 is a relation with three attributes, A,B and X; R2 is a relation with three attributes, E,B and X.



The natural join would be a join where the values in B and X are equal in both R1 and R2. What type of attribute is X? If X is a relation-valued attribute and the columns labelled C and D represent the tuples in X then it seems that the relation values are different in each case. (X in R1 and X in R2 happen to have some of the same tuple values in common but the values of relation X are different in each case).



So the result of the natural join would be an empty relation with a heading of A,B,E,X but with zero tuples.






share|improve this answer















It is not exactly clear what your picture is supposed to represent. I'm going to assume that R1 is a relation with three attributes, A,B and X; R2 is a relation with three attributes, E,B and X.



The natural join would be a join where the values in B and X are equal in both R1 and R2. What type of attribute is X? If X is a relation-valued attribute and the columns labelled C and D represent the tuples in X then it seems that the relation values are different in each case. (X in R1 and X in R2 happen to have some of the same tuple values in common but the values of relation X are different in each case).



So the result of the natural join would be an empty relation with a heading of A,B,E,X but with zero tuples.







share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 23 '18 at 21:16

























answered Nov 23 '18 at 20:34









nvogelnvogel

20.9k12962




20.9k12962













  • Your picture is apt to confuse because it includes some sort of type info in column 3 of the heading when it doesn't for the others. If you're using some convention with a special layout for relation-valued attributes, you should say so. Even if that's maybe what the asker is consciously doing (in headings & values).

    – philipxy
    Nov 23 '18 at 20:47





















  • Your picture is apt to confuse because it includes some sort of type info in column 3 of the heading when it doesn't for the others. If you're using some convention with a special layout for relation-valued attributes, you should say so. Even if that's maybe what the asker is consciously doing (in headings & values).

    – philipxy
    Nov 23 '18 at 20:47



















Your picture is apt to confuse because it includes some sort of type info in column 3 of the heading when it doesn't for the others. If you're using some convention with a special layout for relation-valued attributes, you should say so. Even if that's maybe what the asker is consciously doing (in headings & values).

– philipxy
Nov 23 '18 at 20:47







Your picture is apt to confuse because it includes some sort of type info in column 3 of the heading when it doesn't for the others. If you're using some convention with a special layout for relation-valued attributes, you should say so. Even if that's maybe what the asker is consciously doing (in headings & values).

– philipxy
Nov 23 '18 at 20:47






















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53447928%2fnon-first-normal-form-natural-join-operation%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Wiesbaden

Marschland

Dieringhausen