I see only two reasons why OJB would write values into a timestamp column: 1. you have set the attribute locking="true" in the field-descriptor 2. you are using a ConversionStrategy that modifies the column.
cheers, Thomas
lyl wrote:
Thanks for ketan's response, but I don't think it is caused by mysql, I used p6spy , the spy.log indicate that the insert statement replace null with current time. I think it is ojb who do that job.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
