Oracle SELECT from multiple tables problem
up vote
0
down vote
favorite
Can get all queries to work in an assignment but the last one of 28
- Write a query to show the Task Id, Max Hours and Actual Hours for all task
TASK
taskid (pk)
taskname
givendate
startdate
enddate
maxhours
JOB
taskid (pk,fk)
empid (pk,fk)
hoursspent
Actual hours is hoursspent
It has me stumped, having no trouble with other JOINS but cant get this one to work without column ambigiously defined!
oracle
asked Nov 19 at 0:58
Mike Green
1
add a comment |
up vote
0
down vote
favorite
Can get all queries to work in an assignment but the last one of 28
- Write a query to show the Task Id, Max Hours and Actual Hours for all task
TASK
taskid (pk)
taskname
givendate
startdate
enddate
maxhours
JOB
taskid (pk,fk)
empid (pk,fk)
hoursspent
Actual hours is hoursspent
It has me stumped, having no trouble with other JOINS but cant get this one to work without column ambigiously defined!
oracle
asked Nov 19 at 0:58
Mike Green
1
Please edit the question, and show example data, expected output, and what you have tried. Thanks
– OldProgrammer
Nov 19 at 1:19
1
hint: researchgroup byandmax()&sum(), if joins are no problem it is the group by clause that you now need (it comes after the where clause)
– Used_By_Already
Nov 19 at 1:48
your last comment about ambiguously defined columns suggests you have the same named field in both tables, therefor you need to fully qualify these fields (eg tablename.fieldname not just fieldname). Also have a look at aliasing your tables to save yourself some typing. In most of my roles fully qualifying all fields is a standard to ensure that these problems do not happen.
– Shaun Peterson
Nov 19 at 3:38
Thanks, will try some research and attempt some more options at school tomorrow
– Mike Green
Nov 20 at 3:47
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Can get all queries to work in an assignment but the last one of 28
- Write a query to show the Task Id, Max Hours and Actual Hours for all task
TASK
taskid (pk)
taskname
givendate
startdate
enddate
maxhours
JOB
taskid (pk,fk)
empid (pk,fk)
hoursspent
Actual hours is hoursspent
It has me stumped, having no trouble with other JOINS but cant get this one to work without column ambigiously defined!
oracle
asked Nov 19 at 0:58
Mike Green
1
Can get all queries to work in an assignment but the last one of 28
- Write a query to show the Task Id, Max Hours and Actual Hours for all task
TASK
taskid (pk)
taskname
givendate
startdate
enddate
maxhours
JOB
taskid (pk,fk)
empid (pk,fk)
hoursspent
Actual hours is hoursspent
It has me stumped, having no trouble with other JOINS but cant get this one to work without column ambigiously defined!
oracle
oracle
asked Nov 19 at 0:58
Mike Green
1
asked Nov 19 at 0:58
Mike Green
1
asked Nov 19 at 0:58
Mike Green
1
asked Nov 19 at 0:58
Mike Green
1
asked Nov 19 at 0:58
Mike Green
1
1
Please edit the question, and show example data, expected output, and what you have tried. Thanks
– OldProgrammer
Nov 19 at 1:19
1
hint: researchgroup byandmax()&sum(), if joins are no problem it is the group by clause that you now need (it comes after the where clause)
– Used_By_Already
Nov 19 at 1:48
your last comment about ambiguously defined columns suggests you have the same named field in both tables, therefor you need to fully qualify these fields (eg tablename.fieldname not just fieldname). Also have a look at aliasing your tables to save yourself some typing. In most of my roles fully qualifying all fields is a standard to ensure that these problems do not happen.
– Shaun Peterson
Nov 19 at 3:38
Thanks, will try some research and attempt some more options at school tomorrow
– Mike Green
Nov 20 at 3:47
add a comment |
Please edit the question, and show example data, expected output, and what you have tried. Thanks
– OldProgrammer
Nov 19 at 1:19
1
hint: researchgroup byandmax()&sum(), if joins are no problem it is the group by clause that you now need (it comes after the where clause)
– Used_By_Already
Nov 19 at 1:48
your last comment about ambiguously defined columns suggests you have the same named field in both tables, therefor you need to fully qualify these fields (eg tablename.fieldname not just fieldname). Also have a look at aliasing your tables to save yourself some typing. In most of my roles fully qualifying all fields is a standard to ensure that these problems do not happen.
– Shaun Peterson
Nov 19 at 3:38
Thanks, will try some research and attempt some more options at school tomorrow
– Mike Green
Nov 20 at 3:47
Please edit the question, and show example data, expected output, and what you have tried. Thanks
– OldProgrammer
Nov 19 at 1:19
Please edit the question, and show example data, expected output, and what you have tried. Thanks
– OldProgrammer
Nov 19 at 1:19
1
1
hint: research
group by and max() & sum() , if joins are no problem it is the group by clause that you now need (it comes after the where clause)– Used_By_Already
Nov 19 at 1:48
hint: research
group by and max() & sum() , if joins are no problem it is the group by clause that you now need (it comes after the where clause)– Used_By_Already
Nov 19 at 1:48
your last comment about ambiguously defined columns suggests you have the same named field in both tables, therefor you need to fully qualify these fields (eg tablename.fieldname not just fieldname). Also have a look at aliasing your tables to save yourself some typing. In most of my roles fully qualifying all fields is a standard to ensure that these problems do not happen.
– Shaun Peterson
Nov 19 at 3:38
your last comment about ambiguously defined columns suggests you have the same named field in both tables, therefor you need to fully qualify these fields (eg tablename.fieldname not just fieldname). Also have a look at aliasing your tables to save yourself some typing. In most of my roles fully qualifying all fields is a standard to ensure that these problems do not happen.
– Shaun Peterson
Nov 19 at 3:38
Thanks, will try some research and attempt some more options at school tomorrow
– Mike Green
Nov 20 at 3:47
Thanks, will try some research and attempt some more options at school tomorrow
– Mike Green
Nov 20 at 3:47
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53367038%2foracle-select-from-multiple-tables-problem%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
Please edit the question, and show example data, expected output, and what you have tried. Thanks
– OldProgrammer
Nov 19 at 1:19
1
hint: research
group byandmax()&sum(), if joins are no problem it is the group by clause that you now need (it comes after the where clause)– Used_By_Already
Nov 19 at 1:48
your last comment about ambiguously defined columns suggests you have the same named field in both tables, therefor you need to fully qualify these fields (eg tablename.fieldname not just fieldname). Also have a look at aliasing your tables to save yourself some typing. In most of my roles fully qualifying all fields is a standard to ensure that these problems do not happen.
– Shaun Peterson
Nov 19 at 3:38
Thanks, will try some research and attempt some more options at school tomorrow
– Mike Green
Nov 20 at 3:47