Storing a complex object model in a relational database
has famously been compared to taking apart your car to park it in the garage each
night, and reassembling it the next morning before you drive to work. Huh, cannot
even imagine doing that ... One way to avoid this, is to use object persistence model. As
I wrote , we
(me and my collegues at Axinom) use our Axinom
Business Framework with integrated object persistence. It's nice to have this
functionality today. Another way to avoid the reassembling, is to use ObjectSpaces,
scheduled in Whidbey timeframe. I was wondering about this short timeframe left
for finalizing the interface designs in order to avoid changing a lot of stuff
during 2005 to make it compatible with WinFS. But, here are some hot news about this:
Developers who have been following
the evolution of "ObjectSpaces" – a technology effort building
services supporting object representations of data in relational databases –
will be interested to know that these efforts are being merged with the
Windows code-named “Longhorn” object/data technology “WinFS”.
This decision was made after evaluating the overlapping scenarios that each of these
technologies delivered and firm feedback that developers and architects need a consistent,
long-lived API delivering this functionality.
Interested in finding out more about ObjectSpaces? Here
are some interesting links related to this topic:
Previous Topic
