Another unconfirmed use case I heard of, different than the one assumed in Pinaki's fix, is that @Versions is specified when an entity's fields are spread across multiple secondary tables. The primary table and each secondary table have their own version columns, and when any attribute of a table is updated, JPA tracks the corresponding version field for that table.
Thanks, Dinkar On Mon, Aug 25, 2008 at 10:25 AM, Pinaki Poddar <[EMAIL PROTECTED]> wrote: > > Hi Craig, > Perhaps, in legacy situations, where the JPA application may not own all > the version columns and other apps may be updating one or more of them. But > I can not remember seeing a real use case. > > Regards -- > -- > View this message in context: > http://n2.nabble.com/%40VersionColumns-usage-tp736463p782044.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. > >
