Sybase has timestamp just for that.
.V
[EMAIL PROTECTED] wrote:
I would agree that this would be an easy implementation that I would
prefer. The problem is that I am working with an existing Data Model
that I inherited and I cannot change without having an enormous impact
on multiple groups and application UI's. (Not something that I am ready
to propose) This is the model that I am stuck with unfortunately.
I think I have a solution to the problem but I feel that it is a very
dirty one. I could define an additional field in each domain object and
call it 'now', which would get the current timestamp, set by the Dao,
just prior to performing the insert. I would then update the value in
the SQL as follows:
update customer set
name = #name#,
record_date = #now#,
...
where
id = #id#
and
record_date = #recordDate#
Then if the update was successful I could have the Dao update the record
date with the value of now. It's dirty, so I am in hopes that someone
has a better solution for me.
Thanks...
Chris Mathrusse
[EMAIL PROTECTED]
Sybase, Inc
One Sybase Drive
Dublin, CA 94568
(925) 236-5553
