Re: Storing values that are relationship IDs (or how should i make anabstract history method)

Do you know where I can find info on implementing this? I'm familiar
with journaling as a lower level feature but not something viewable by
a user.

Thanks for the suggestion.

--matt

On 2/8/06, Joshua Marker <[email protected]> wrote:
>
> I see you've worked on this a lot. Has anyone suggested you implement
> it with journaling, which can do all this automatically? You might
> find it much easier.
>
>
> On Jan 18, 2006, at 21:04, Matt Kime wrote:
>
> > Here's the idea...
> >
> > I'm trying to create an abstract class to implement a history
> > system. I can have a object return its entity name and its
> > attribute values. I want to store these in a table that consists of:
> >
> > entityName
> > entityID
> > entityValue
> >
> > ---
> >
> > this way any class based on this abstract class will be able to
> > save its history. while this will work perfectly fine for
> > attributes, i'm concerned as to how it will work with to-one
> > relationships. yes, i can save the id value in the entityValue
> > field. but how will i turn this into a relationship again?
> >
> > i hope i've explained this well.
> >
> > thanks,
> > matt
> >
> >
> > _______________________________________________
> > WebObjects-dev mailing list
> > [email protected]
> > http://www.omnigroup.com/mailman/listinfo/webobjects-dev
>
>
>
> ________________________________________________________________
> This message could have been secured by PGP Universal. To secure
> future messages from this sender, please click this link:
>
> https://keys.pgp.com/b/b.e?r=mattkime%40gmail.com&n=tWwfcF2nzI5VLwz%2BFbQq8A%3D%3D
>