Version compatibility problems for persistent data storage

/ ** 
* combat arms, containing the final battle property
*
* After a sequence of such objects will be stored in the database, using VersionFieldSerializer backward compatibility
* Do not delete or modify an existing field, existing field, new field need to use the mark @Since version, the version number has been marked can not be modified
* /

      @Since (value = 1) 
@Deprecated ( "This is the stuff of the old days")
var Stage: Int = 0, Junjun order before and after //

      @Deprecated (message = "treasure revision, a hero not only a treasure and treasure type", The replaceWith = ReplaceWith ( "treasureMessage")) 
Val Treasure: the HashMap <TreasureType, TreasureMessage> = Maps.newHashMapWithExpectedSize (. 4),

Guess you like

Origin www.cnblogs.com/vana/p/11023304.html