This post originated from an RSS feed registered with Java Buzz by David Rolfe. Original Post: ROWID Madness Feed Title: OrindaBlog - Orinda Software's Corporate Blog Feed URL: http://www.jroller.com/rss/orindasoft Feed Description: We're in the business of creating products that make it easier to work with Oracle, Java and JDBC. We want this blog to be something more than a stream of product-related propaganda - our intention is two-thirds of the content will be of general relevance to people who work with Oracle, Java and PL/SQL. Entries to this blog will be made as and when we have information that we think our readers would be interested in. Latest Java Buzz Posts Latest Java Buzz Posts by David Rolfe Latest Posts From OrindaBlog - Orinda Software's Corporate Blog

For years the first of my interview questions for Oracle developers has been one in which I ask them to explain why it's a bad idea to use the ROWID of table 'A' as a foreign key to table 'B'. This is not hard for a competant person to answer, as ROWID changes when you import the data into another database which will happen sooner or later. It never occured to me that someone could be crazy enough to actually do this, but someone has.