The used SELECT statements have a different number of columns

后端 未结 5 1669
执笔经年
执笔经年 2021-01-11 13:28

For examples I don\'t know how many rows in each table are and I try to do like this:

SELECT * FROM members 
UNION 
SELECT * FROM inventory

5条回答
  •  不思量自难忘°
    2021-01-11 13:40

    you could do

    SELECT *
    from members
    UNION
    SELECT inventory.*, 'dummy1' AS membersCol1, 'dummy2' AS membersCol2
    from inventory;
    

    Where membersCol1, membersCol12, etc... are the names of columns from members that are not in inventory. That way both queries in the union will have the same columns (Assuming that all the columns in inventory are the same as in members which seems very strange to me... but hey, it's your schema).

    UPDATE:

    As HLGEM pointed out, this will only work if inventory has columns with the same names as members, and in the same order. Naming all the columns explicitly is the best idea, but since I don't know the names I can't exactly do that. If I did, it might look something like this:

    SELECT id, name, member_role, member_type
    from members
    UNION
    SELECT id, name, '(dummy for union)' AS member_role, '(dummy for union)' AS member_type
    from inventory;
    

    I don't like using NULL for dummy values because then it's not always clear which part of the union a record came from - using 'dummy' makes it clear that the record is from the part of the union that didn't have that record (though sometimes this might not matter). The very idea of unioning these two tables seems very strange to me because I very much doubt they'd have more than 1 or 2 columns with the same name, but you asked the question in such a way that I imagine in your scenario this somehow makes sense.

提交回复
热议问题