Hi, filippo wrote: > I have two tables like these: (this is an example, the actual tables > have diffferent fields and meanings) > > TABLE1 > id > person_name > date_arrival > date_departure > > TABLE2 > id > car_description > date_arrival > date_departure > > I'd like to make a query to have such resulting table > > RESULTING_TABLE > id > person_name > car_description > date_arrival > date_departure > > the id is the primary key for the three tables and it's unique for the > three (id in table1 cannot be in table2, I use the same counter to > generate the id for table1 and table2).
SELECT id, person_name, NULL AS car_description, date_arrival, date_departure FROM TABLE1 UNION SELECT id, NULL AS person_name, car_description, date_arrival, date_departure FROM TABLE2 ORDER BY <what you want> But be careful, w/o constraints there's no guarantee that the id's are really unique on both tables! HTH, -tb ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match