I have tables which have the following set of fields in all of them.
createdBy INTEGER
createdOn DATE
updatedBy INTEGER
updatedOn DATE
Using turbine OM class generation, I was wondering what was the best way
to go about setting these fields when inserting, updating, deleting
these fields.
Is there an object which can be registered, associated with the
insert/delete/update actions on the tables to transparently handle
setting these fields? Or some other ideas?
- Viru
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>