24 Şubat 2012 Cuma 23:26
The Upsert feature in Table Storage was announced and released way back at //Build/ (along with a number of other features). And here we are almost 6 months later and the StorageClient assembly in SDK v1.6 still doesn't support this new feature (though it does have the new Queue features)?
Anyone know when we might expect this? I am about to embark on a project that needs them and I'd rather not have to use the sample code from the announcement blog post.
25 Şubat 2012 Cumartesi 00:05
This post does describe how this is supported although the support is not very explicit.
I have written an alternate windows azure table storage client which supports ‘upsert’ very explicity and many other features not supported by the Microsoft client. Out of the box features include support for enums, arrays/lists, properties larger than 64K, serialization, schema less types, context free etc. You can read more about it at www.lucifure.com.
25 Şubat 2012 Cumartesi 01:38
Hi - thanks for the question. The only code that was temporary in the blog post I think you're referencing (http://blogs.msdn.com/b/windowsazurestorage/archive/2011/09/15/windows-azure-tables-introducing-upsert-and-query-projection.aspx) was the code that helped change the version. If you're using SDK 1.6, this code is no longer necessary, as 1.6 already sends the updated version. All of the other code uses built in .NET Data Services support for Upsert, and is our supported method of performing upsert operations. Is there something else you're looking for?
It's worth noting that there's another example of them in our "How to Use the Table Storage Service" article here: http://www.windowsazure.com/en-us/develop/net/how-to-guides/table-services/#insert-entity.
Please let us know if you have any additional questions.
- Yanıt Olarak İşaretleyen Curious George 25 Şubat 2012 Cumartesi 16:46
25 Şubat 2012 Cumartesi 16:46Ah, completely my fault. I thought there was much more to it than that and I saw no reference to the update for using the new 2011-08-18 version in the v1.6 SDK. Sorry for the confusion, and thanks for setting me straight!