开发者

SQL join basic questions

开发者 https://www.devze.com 2023-02-04 01:40 出处:网络
When I have to select a number of fields from different tables: do I always need to join tables? which tables do I need to join?

When I have to select a number of fields from different tables:

  1. do I always need to join tables?
  2. which tables do I need to join?
  3. which fields do I have to use for the 开发者_开发百科join/s?
  4. do the joins effects reflect on fields specified in select clause or on where conditions?

Thanks in advance.


Think about joins as a way of creating a new table (just for the purposes of running the query) with data from several different sources. Absent a specific example to work with, let's imagine we have a database of cars which includes these two tables:

CREATE TABLE car (plate_number CHAR(8), 
                  state_code CHAR(2), 
                  make VARCHAR(128), 
                  model VARCHAR(128),);

CREATE TABLE state (state_code CHAR(2),
                    state_name VARCHAR(128));

If you wanted, say, to get a list of the license plates of all the Hondas in the database, that information is already contained in the car table. You can simply SELECT * FROM car WHERE make='Honda';

Similarly, if you wanted a list of all the states beginning with "A" you can SELECT * FROM state WHERE state_name LIKE 'A%';

In either case, since you already have a table with the information you want, there's no need for a join.

You may even want a list of cars with Colorado plates, but if you already know that "CO" is the state code for Colorado you can SELECT * FROM car WHERE state_code='CO'; Once again, the information you need is all in one place, so there is no need for a join.

But suppose you want a list of Hondas including the name of the state where they're registered. That information is not already contained within a table in your database. You will need to "create" one via a join:

car INNER JOIN state ON (car.state_code = state.state_code)

Note that I've said absolutely nothing about what we're SELECTing. That's a separate question entirely. We also haven't applied a WHERE clause limiting what rows are included in the results. That too is a separate question. The only thing we're addressing with the join is getting data from two tables together. We now, in effect, have a new table called car INNER JOIN state with each row from car joined to each row in state that has the same state_code.

Now, from this new "table" we can apply some conditions and select some specific fields:

SELECT plate_number, make, model, state_name
FROM car
INNER JOIN state ON (car.state_code = state.state_code)
WHERE make = 'Honda'

So, to answer your questions more directly, do you always need to join tables? Yes, if you intend to select data from both of them. You cannot select fields from car that are not in the car table. You must first join in the other tables you need.

Which tables do you need to join? Whichever tables contain the data you're interested in querying.

Which fields do you have to use? Whichever fields are relevant. In this case, the relationship between cars and states is through the state_code field in both table. I could just as easily have written

car INNER JOIN state ON (state.state_code = car.plate_number)

This would, for each car, show any states whose abbreviations happen to match the car's license plate number. This is, of course, nonsensical and likely to find no results, but as far as your database is concerned it's perfectly valid. Only you know that state_code is what's relevant.

And does the join affect SELECTed fields or WHERE conditions? Not really. You can still select whatever fields you want and you can still limit the results to whichever rows you want. There are two caveats.

First, if you have the same column name in both tables (e.g., state_code) you cannot select it without clarifying which table you want it from. In this case I might write SELECT car.state_code ...

Second, when you're using an INNER JOIN (or on many database engines just a JOIN), only rows where your join conditions are met will be returned. So in my nonsensical example of looking for a state code that matches a car's license plate, there probably won't be any states that match. No rows will be returned. So while you can still use the WHERE clause however you'd like, if you have an INNER JOIN your results may already be limited by that condition.


Very broad question, i would suggest doing some reading on it first but in summary: 1. joins can make life much easier and queries faster, in a nut shell try to 2. the ones with the data you are looking for 3. a field that is in both tables and generally is unique in at least one 4. yes, essentially you are createing one larger table with joins. if there are two fields with the same name, you will need to reference them by table name.columnname


do I always need to join tables?

No - you could perform multiple selects if you wished

which tables do I need to join?

Any that you want the data from (and need to be related to each other)

which fields do I have to use for the join/s?

Any that are the same in any tables within the join (usually primary key)

do the joins effects reflect on fields specified in select clause or on where conditions?

No, however outerjoins can cause problems


(1) what else but tables would you want to join in mySQL?

(2) those from which you want to correlate and retrieve fields (=data)

(3) best use indexed fields (unique identifiers) to join as this is fast. e.g. join retrieve user-email and all the users comments in a 2 table db (with tables: tableA=user_settings, tableB=comments) and both having the column uid to indetify the user by select * from user_settings as uset join comments as c on uset.uid = c.uid where uset.email = "test@stackoverflow.com";

(4) both...

0

精彩评论

暂无评论...
验证码 换一张
取 消