[boost] Re: Re: Serialization to relational table

From: Bohdan (warever_at_[hidden])
Date: 2002-11-19 08:59:33

"Joachim Achtzehnter" <joachim_at_[hidden]> wrote in message
news:Pine.LNX.4.44.0211181348510.13643-100000_at_penguin.kraut.ca...
> Today, in a message to boost, Vladimir Prus wrote:
> >
> > Bohdan wrote:
> > >
> > > serialization: Object <-> Relational tuple (object-relational mapping).
> >
> > Wouldn't there be a problem with converting object with variable size?
> > How can you store vector<int> in a relational database? I don't see an
> > easy way.
>
> You are raising a good point. What this ultimately boils down to is the
> realization that mapping Object to Tuple is problematic.
>
> This doesn't mean that the relational model is a bad choice as a target
> model for a persistent store. On the contrary, it is probably the best
> model to use for this purpose. The problem is only the assumption that
> Object (or better: type) maps always to Tuple. Recent developments in
> relational theory suggest that it is the Domain concept ("column type")
> that should be seen as the closest equivalent to "Object Type". Refer to
> recent writings by Chris Date (books and also papers, the latter
> accessible on the Web) for the theory behind this, and why the Object <=>
> Tuple identification is a mistake.

Sure, i know about it. The main problem is inheritance and pointer members,
but i have some ideas how to deal with them. My first letter intention was just
to
describe idea.

regards,
bohdan