If there's a new book with this title it is instantly on my radar. I just had a quick look on it in www.books24x7.com. I did a full text search on the words

• migration - because migrating tables based on object types is evil (it was in 8i, 9i and still is in 10g)
• evolution - because type evolution (related to migration) is still an unsolved topic in Oracle
• XML - because the relationship between relational data, object hierarchies and XML data is one strong argument to use object types in Oracle

I've found: Nothing! Having a look around in the book I came to the conclusion that this is one of these books you won't need if you read the Oracle documentation carefully - It's all there, including examples.

A little late I just had a look into the LINQ video with Anders Hejlsberg on channel9.msdn.com.

On one side I must say: Ok, these client developers now also can do what we - 'the DB guys' are doing for years using PLSQL, T-SQL, Pro*C and what not: Using sets in a high level set oriented manner instead of multiple loops.

On the other side, being busy in both worlds since years, I must say: Well done! This is the right way to go, this fills a lot of existing gaps in the OO world with paradigms coming from the relational world. I do now have an idea of why Microsoft cancelled the ObjectSpaces project some time ago. Using the results of Hejlsbergs (and others) ideas from Delphi 1 until today (VCL DataSets, .NET DataSets etc.) I'm convinced that I will enjoy working with LINQ.

Today I needed to generate some test data. I wanted to join 2 uncorrelated result sets having the same number of rows. I couldn't find an easier solution than generating 2 inline views and join them together by rownum.



Could that be done in a simpler way?