Re: compare 2 tables in sql - Mailing list pgsql-sql

From Tena Sakai
Subject Re: compare 2 tables in sql
Date
Msg-id FE44E0D7EAD2ED4BB2165071DB8E328C0378F142@egcrc-ex01.egcrc.org
Whole thread Raw
In response to compare 2 tables in sql  ("Tena Sakai" <tsakai@gallo.ucsf.edu>)
List pgsql-sql
<p><font size="2">Hi Jonah,<br /><br /> > Still, you should UNION the result of<br /> > both exceptions into a
singleresult set.<br /><br /> Great suggestion.  Many thanks.<br /><br /> Regards,<br /><br /> Tena Sakai<br />
tsakai@gallo.ucsf.edu<br/><br /><br /> -----Original Message-----<br /> From: Jonah H. Harris [<a
href="mailto:jonah.harris@gmail.com">mailto:jonah.harris@gmail.com</a>]<br/> Sent: Thu 3/20/2008 12:21 PM<br /> To:
TenaSakai<br /> Cc: pgsql-sql@postgresql.org<br /> Subject: Re: [SQL] compare 2 tables in sql<br /><br /> On Thu, Mar
20,2008 at 1:44 PM, Tena Sakai <tsakai@gallo.ucsf.edu> wrote:<br /> >  Just a postscript.  It is important to
check<br/> >  both ways.  Because (sometimes) vice versa is<br /> >  not necessarily true.  Case in point
below:<br/><br /> Yes, I'm well aware of that.  Still, you should UNION the result of<br /> both exceptions into a
singleresult set.<br /><br /> --<br /> Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324<br /> EnterpriseDB
Corporation| fax: 732.331.1301<br /> 499 Thornall Street, 2nd Floor | jonah.harris@enterprisedb.com<br /> Edison, NJ
08837| <a href="http://www.enterprisedb.com/">http://www.enterprisedb.com/</a><br /><br /></font> 

pgsql-sql by date:

Previous
From: "Jonah H. Harris"
Date:
Subject: Re: compare 2 tables in sql
Next
From: "Tena Sakai"
Date:
Subject: Re: compare 2 tables in sql