RE: rowid value

From: Powell, Mark <mark.powell2_at_hp.com>
Date: Fri, 8 Aug 2014 18:55:01 +0000
Message-ID: <1E24812FBE5611419EFAFC488D7CCDD126EDE330_at_G6W2491.americas.hpqcorp.net>

Jared said, “Identifying which 'duplicate' to delete it [sic] not always straight forward.”

No it isn’t since the non-key columns may differ and in some cases you actually should determine which row to save based on the non-key data. Worse is when you discover you need some data from multiple rows.

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Jared Still Sent: Friday, August 08, 2014 2:23 PM
To: kibeha_at_gmail.com
Cc: Hemant-K.Chitale_at_sc.com; Brian Zelli; ORACLE-L Subject: Re: rowid value

On Wed, Aug 6, 2014 at 1:15 AM, Kim Berg Hansen <kibeha_at_gmail.com<mailto:kibeha_at_gmail.com>> wrote: If the idea of deleting the "higher" ROWID is to delete the "newest" row, that is not at all certain. But if the rows are identical duplicates, that shouldn't matter ;-)

Probably this is already stated somewhere in this thread, but it bears repeating.

Duplicate refers to PK/UK, not the row.

Identifying which 'duplicate' to delete it not always straight forward.

Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist Sr Oracle DBA at Pythian
Pythian Blog http://www.pythian.com/blog/author/still/ Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com

--
http://www.freelists.org/webpage/oracle-l

Received on Fri Aug 08 2014 - 20:55:01 CEST