Can we safely use the table storage Timestamp column? RRS feed

  • Question

  • I read in the table storage doc that the Timestamp is "Every entity has a version maintained by the system." and "Timestamp is a read-only system maintained property which should be treated as an opaque property " but the TableServiceEntity class has it as the following, which seems to allow setting a value to it.
    public DateTime Timestamp { getset; }

    So I'm just wondering if we can rely on this Timestamp column as part of our logic?



    Tuesday, May 10, 2011 10:21 PM


  • I think the word opaque is a good indicator that you should not use it as part of your logic. Even though it may well be fine to use it, Microsoft is presumably reserving the right to change the way in which it is generated at some point in the future (that may well never come).
    • Marked as answer by Wenchao Zeng Tuesday, May 17, 2011 2:35 AM
    Tuesday, May 10, 2011 10:54 PM