You're right. This will probably indeed do what we need until the reliable
dirty checking algorithm is complete and we need to update the database
anyway. We'll keep you posted if we can think of another approach that might
be a cleaner implementation and thanks again for the help.
Cheers,
Tim Ruppert && Ben Cox
Keith Visco wrote:
> Keith Visco wrote:
> >
> > Margaret,
> >
> > Your solution is a good one...but you can also use it for persisting the
> > timestamps if you want to by simply combining both your approach, and
> > Ben's....
> >
> > public abstract class JDOBaseClass {
>
> Opps...don't forget to add the implements TimeStampable...
>
> :-)
>
> --Keith
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
