RE: Easy way to determine if two tables contain the same data -- MIDRANGE-L

Don't you just miss the days when IBM actually cared enough about the
product line to have a real release announcement day in which they brought
in all the local users for a half/full day of announcement information will
ALL the new goodies that were being announced, features, SOFTWARE, LANGUAGE
FEATURES, etc???

I guess there's just not enough folks left around to warrant those kinds of
meetings anymore...

DR2

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dave
Sent: Friday, March 29, 2013 5:10 AM
To: Midrange Systems Technical Discussion
Subject: Re: Easy way to determine if two tables contain the same data

For years I would have used UNION to see if the tables were the same, then
investigate with EXCEPTION JOIN, often a lot more work. I'm astonished that
this dates from V5R4. I wonder what other goodies are still waiting to be
discovered.

2013/3/29 Peter Connell <Peter.Connell@xxxxxxxxxx>

Charles,
I did not know that.
Thanks.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Friday, 29 March 2013 12:29 p.m.
To: Midrange Systems Technical Discussion
Subject: Easy way to determine if two tables contain the same data

D
on't know if this technique has ever been posted here or not, but I ran
across the technique last night on a DB2 LUW forum and it works just fine
on DB2 for IBM i...

If you have a need to compare the contents of two tables to determine if
they match, here's the easy way.
select * from table1
EXCEPT
select * from table2

In my case, I was refactoring some code and wanted to make sure that the
output was still the same.

You can even use it on two different version of a table...you just have to
do a bit more typing. Example: Original table has fld1, fld2 and new
table has fld1,fld2, fld3.

select * from origtable
EXCEPT
select fld1,fld2 from newtable

I was doing it on 7.1, but according to the manual, except is supported
starting at v5r4.

Cavats: the tables must have a primary key; or be a uniquely keyed
physical.

HTH,
Charles
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

############################################################################
#########

This correspondence is for the named person's use only. It may contain
confidential
or legally privileged information, or both. No confidentiality or
privilege is waived
or lost by any mistransmission. If you receive this correspondence in
error, please
immediately delete it from your system and notify the sender. You must not
disclose,
copy or rely on any part of this correspondence if you are not the
intended recipient.
Any views expressed in this message are those of the individual sender,
except where
the sender expressly, and with authority, states them to be the views of
Veda.
If you need assistance, please contact Veda on either :-
Australia 1300-762-207 or New Zealand +64 9 367 6200
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.