locked
Handling error in entity group transaction on Azure Table RRS feed

  • Question

  • I have noted a difference not described in http://msdn.microsoft.com/en-us/library/gg433135.aspx about the error returned in case of batch insert between emulator and Azure table storage:

    in case of error the sequence number of the command that caused the entire transaction to fail, in Storage Emulator return always 0, but in Azure is correct.

    Currently I have a test on the index returned in the error message that fails with the emulator, so I have due disable it.

    Someone else has noted the same problem?

    Is there some setting to do to workaround the problem?

    Thanks.

    Cristiano

    Friday, July 1, 2011 10:26 AM

Answers