Using optimistic locking with timestamp_column_strategy means an entity will be added a timestamp column that will be used for optimistic locking. It can't be accessed by application. (Indeed, it should be possible to mention it in a QL statement)
If you want a CMP timestamp field to be used in optimistic locking, then you should have timestamp CMP field and use read- or modified-strategy and update timestamp value yourself or let the db update it. alex Monday, March 31, 2003, 6:08:06 PM, you wrote: SM> Hi, SM> I am currently testing Optimistic locking with the Timestamp Strategy. My findings are that the timestamp column cannot be a CMP field otherwise the insert SQL will include it 2 times. SM> Any thoughs anyone? SM> Thanks! SM> Simone ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
