People seemed to like the idea that you can store CLR types inside Yukon.
I like the idea too, but don't get confused.. this is not turning Yukon into an OO-Database and it's not giving Yukon a way to automatically persist your domain objects (i.e., your Customer or your Order). It will work for complex types that have no meaning when split into its simple components, like the 'Point' type.
Unless they do things like letting you create indexes by these object's fields, and create integrity relations between them, etc, the way to work with data will still be the old-and-great relational model.
The Yukon implementation seems to follow Chris Date's Third Manifesto, where he says that in the relational model objects map to domains, not to relations, as we usually do when building our data access layers.
2:51:13 AM 
|
