Jump to content

Recommended Posts

table1

 

id

headline

 

table2

 

id

parent

image

 

 

Currently I've got

 

SELECT a.headline, b.image FROM table1 a LEFT JOIN table2 b ON b.parent=a.id 

 

but what I want to do is list all the headlines from table 1 and display one image from table2 for each headline...

 

Does anybody know where I'm going wrong here?

Link to comment
https://forums.phpfreaks.com/topic/58214-solved-left-join-limit/
Share on other sites

why do u need a join if  u have a id corresponding to every parent.

 

SELECT a.headline, b.image FROM table1 a , table2 b where b.parent=a.id

 

if u don't  have corresponding parent in table2 for each id then

 

Select headline from table1 LEFT JOIN (select image from table2) ON b.parent=a.id

 

Does anybody know where I'm going wrong here?

 

The query looks fine.  What are or aren't you getting that is unexpected?

 

 

 

Select headline from table1 LEFT JOIN (select image from table2) ON b.parent=a.id

 

A) Why would you use a subquery when you can use a JOIN?  b)  Why would you do both?  c) You need to select id in the subquery if you want to reference it in the outer query.  D) You need to alias the table and the subquery before using those aliases in the ON clause.

Yes , I forgot to use alias names  ;)

 

Select headline from table1 as a LEFT JOIN (select image from table2 as b)  ON b.parent=a.id

 

Why would you do both?

I just given a alternative to what oldschool has written. Is there any thing wrong with the query , I mean will it not give expected results?. I know it make a difference performence prospective.

Why would you do both?

I just given a alternative to what oldschool has written. Is there any thing wrong with the query , I mean will it not give expected results?. I know it make a difference performence prospective.

 

Yes, you need to select the id in the subquery if you want to reference it outside in the ON clause.  (SELECT id,image FROM table2) AS b....etc.  But since this is an easy LEFT JOIN, there's not really a need for subqueries, which, yes, tend to be less efficient than JOINs.

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.