On Fri, 24 Sep 2010, luuk34 wrote: > you mean something like: > select id1, id2 from callprog a where id1 not in (select b.id1 FROM > callprog b where b.id1=a.id1 );
Yeah; much better. > But what is there is more than 1 column? it will grow in complexity when > you have a lot of columns..... My understanding of the original problem was that rows were about the same, so finding a common column in db1 which was not in db2 was the need. As long as there is one unique column common to both tables it makes no difference how many other columns there are in each one. Rich _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
