Jump to content
  • Announcements

    • boen_robot

      Guidelines and Netiquette   03/28/2017

      Posting Problems:   Having problems posting your topic? Read through this: To join, you agree to our terms and conditions and fill out and submit a registration form. An activation email will be sent to your email adress, so you'll need to verify your account. After that the account has to be validated by one of the moderators. This will mean that it can take up to a day to be activated. A couple of things to remember to ensure approval: Don't use an email address in one of those $2 four character .com domains eg. xyds.com. These will be deleted and the domain added to the banned list. Don't use an email address that is within a domain with a bad reputation for spam. A Google search is run on every email address and email domain. Don't sign up with an email address that doesn't exist, doesn't work or requires the sender to answer a quiz before their email can get to you. Put your country and or state and city in the signup form. Blank forms will go to the botton of the "to do" list. And make sure that your email address and your country match, saying you're from Alabama and using a .ru email address is not going to get you activated. After a membership is activated the first few posts will be monitored. Posting spam or unapproved topics described in the agreement results in an immediate ban. The email provider and the IP addresses associated with the account will be banned and all posts will be deleted. These strict measures have been deemed necessary to hinder spam. Sorry for any inconvenience this causes, but it's not liable to change. If, after reading this, you still can't post and don't understand why, contact one of the Moderators listed here.   Topic Guidelines   Including the following information can expedite an accurate response from board members: Must be a Specific Problem or Question related to web design and development Include Code in Question (wrap with   for small blocks of code and for longer blocks   ) Include Code Author Include Extra Notes/Modifications/Attempts Include web link to page/file when possible Content Guidelines   You may not post, upload, link to, or email any Content that contains, promotes, gives instruction about, or provides prohibited Content. Prohibited Content includes any Content that breaks any local, state, county, national or international law. Prohibited Content also includes: No direct or indirect advertising or websites, forums, products, services No hijacking of posts (do not post your question in someone elses) Content that infringes upon any rights [ex. MP3s and ROMs] (including, but not limited to, copyrights and trademarks) Abusive, threatening, defamatory, racist, or obscene Viruses or any other harmful computer software False Information or libel Spam, chain letters, or Pyramid schemes Gambling or Illicit drugs Terrorism Hacking or cheating for internet/online games Warez, Roms, CD-Keys, Cracks, Passwords, or Serial Numbers Pornography, nudity, or sexual material of any kind Excessive profanity Invasive of privacy or impersonation of any person/entity Hacking materials or information Posting Tips   There are more BBcodes than there are buttons for on the reply menu. To get the full list, click "BB Code Help" underneath the clickable smilie face menu. Use   for small snippets of code Use   for lengthy snippets of code Use   if your snippet is HTML (optional) Use   if your snippet is SQL (optional) Rules of Conduct   Be nice. There's no need for calling someone stupid if they ask an 'easy' question. Keep your avatars and signatures absolutely child friendly. We have a younger audience on this forum. Keep your language appropriate for the same reason above. Do not PM moderators for help on the forum. Post on the topic, or create a new one.   Spam:   Recently, as you have all without doubt noticed, we have had lots of spam and advertisement on the forum. Therefore, we'd like to alert you as to what to do when you have found any of the aforementioned annoying messages: it. Immediately. Give a clear reason, please, if the advertising is not evident. DO NOT POST! Report, let the post stay as is, and we will get to it, meanwhile if you continue to post as normal in the other threads, it won't be on the top so long. Refrain from PMing the member. This won't help at all, as they are most likely spambots anyway. Thank you.       Images in signatures:   After thinking of users on dial-up, we have decided to enforce the following rules regarding signatures. Please pay heed to them. Respecting these rules is respecting the members on this forum with dial-up. Signature rules: No animated images AT ALL. No matter the amount of animation. Maximum image widthxheight: 300x150 Maximum image (file) size: 15kb Use calm colors. Do not use highly contrasting images in your signature, as this can get really annoying when seeing several posts from one member in the same thread. The same prohibited content goes for images as for posts. Lastly, use common sense. No lengthy signatures please. Save us some scrolling. Thank you.       Links in signatures:   Please understand that w3schools.com only exists because of voluntary work and is barely supported by the advertising littered throughout the tutorials and the forum. So, please, stop advertising other sites. DO not post links that drive traffic away from the w3schools domain - especially to a site that offers similar if not identical information. Please help support the site by keeping individuals on it. Thank you. Here are some guidelines as to what you can put in your signature: w3schools links --> allowed w3.org links --> allowed browser links --> allowed html editor links --> allowed personal sites --> allowed tutorial sites competing with w3schools --> NOT allowed sites completely irrelevant to webprogramming and this forum --> NOT allowed   Thanks for understanding, and for taking the time to read this. ~W3Schools Modstaff~
iwato

SELECT JOIN - A Failed Query

Recommended Posts

Before i implement the suggested code I have several questions.

Firstly,  I have noticed that the number of columns and their respective definitions must match when combining SELECT statements with the UNION operator.  Does this mean that I must repeat the phrase "p.id, p.usertype, p.username, c.userbio" for each SELECT statement similarly combined.

Secondly, the aliases in the proposed complementary statement are declared after they are used.  This suggests that there is such a thing as scope in their application.  Does the scope of the alias extend beyond the SELECT statement in which it is employed?  Does it, for example, apply to the entire SQL statement?

Thirdly, is there a pecking order in the use of SELECT statements.  Does the first SELECT statement determine what is returned for all subsequent SELECT statement?  Or, does each SELECT statement determine for itself what will be returned.

Finally, although I can understand how designating specific columns would reduce the redundancy in the result set, I cannot understand why it would cause values to appear that have not already appeared with the use of the * wildcard operator. Can you explain this?

Although i can well appreciate the need for the speedy and orderly storage and retrieval of information, my mind is not built like a symmetric associative array, and I am having trouble dealing with the matrix-like nature of SQL and its Chinese-like grammatical syntax.

Roddy

Share this post


Link to post
Share on other sites

Also, provided that the row data contained within a table column is compatible with the new definition is it possible to redefine a MySQL column without destroying the data?

Roddy

Share this post


Link to post
Share on other sites

Firstly,  I have noticed that the number of columns and their respective definitions must match when combining SELECT statements with the UNION operator.  Does this mean that I must repeat the phrase "p.id, p.usertype, p.username, c.userbio" for each SELECT statement similarly combined.

Yes, you need the same number and type of columns returned.  You don't need to use the same table aliases necessarily, but it makes sense to use the same column names.

Secondly, the aliases in the proposed complementary statement are declared after they are used.  This suggests that there is such a thing as scope in their application.

That's not a correct assumption, if you remove the table aliases but keep them in the list of columns you'll get an error indicating that it doesn't know what p or c is.

Does the scope of the alias extend beyond the SELECT statement in which it is employed?

In that specific example, I don't think so, I think those aliases only apply to the select query where they are used.  I could be wrong about that though, you might be able to use one in the other select query, but I don't think that would work.

Or, does each SELECT statement determine for itself what will be returned.

Yes.

I cannot understand why it would cause values to appear that have not already appeared with the use of the * wildcard operator.

It won't, it's just being explicit about what you're asking for.  If you wanted each ID from the two tables separately, for example, you should give each one a unique alias instead of returning 2 columns with the same name.

Also, provided that the row data contained within a table column is compatible with the new definition is it possible to redefine a MySQL column without destroying the data?

If you change the data type of a column and there is existing data, MySQL will attempt to convert the data to the new data type.  There are various rules for converting data between types.  This is also called casting.  You can also explicitly convert data during a SQL query, there are functions to do that.  Those are the same functions that MySQL would use if you change the data type of a column.

  • Thanks 1

Share this post


Link to post
Share on other sites

I misread what you wrote, I thought you wrote "there is no such thing as scope".  Yes, SQL queries have a scope.

  • Like 1

Share this post


Link to post
Share on other sites

ALMOST THERE?

There is an improvement, but i am still not there as the procedure returns NULL for the field userbio.

(SELECT p.id, p.usertype, p.username, c.userbio
	FROM parent_table AS p
	LEFT OUTER JOIN child_table AS c 
		ON c.id = p.id
		WHERE p.id = 10)

UNION 

(SELECT pu.id, pu.usertype, pu.username, cu.userbio
		FROM parent_table AS pu 
		LEFT OUTER JOIN child_table AS cu
			ON cu.id = pu.id
			WHERE pu.id IN (SELECT ref
							FROM ref_table
							WHERE ref_table.id = 10)
)

Output

id	usertype	username	userbio
10	3			david		NULL
4	3			tim			NULL
6	1			liz			NULL

Never mind.  It works.  For some reason the listed data was never entered into the child_table.  Alas,  I am a happy dummy!

Roddy :rolleyes:

Edited by iwato

Share this post


Link to post
Share on other sites
Quote

In that specific example, I don't think so, I think those aliases only apply to the select query where they are used.  I could be wrong about that though, you might be able to use one in the other select query, but I don't think that would work.

It turns out that the aliases must be repeated for each SELECT and JOIN statement, but it makes no difference whether they are the same or different for each SELECT and JOIN statement.

Roddy

Share this post


Link to post
Share on other sites

Yeah, I wouldn't think that the aliases would expand over the union because each of those select queries stands alone.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×