Add TableStorage LINQ query support for Select, Count and Contains
Critical functions such as Select, Count and Contains are not currently available when querying TableStorage data.
If I only want a total number of rows that match a certain criteria I have no choice but to retrieve the data, count it and throw it away.
Adding support for Select would also help with heavy queries by only returning the data selected from a query.
Contains would be useful for searching. Using the Compare function is annoying.
Submit a Regex to search String Columns of Table Storage in the $filter. You could have a limit to the complexity of the Regex, but i think the query timeout should be sufficient enough to prevent a Regex being to complex to process on the first 1000 records matched.
This feature would allow for very efficient, complex text searches, and would likely not take very long to implement in Table Storage.
The table storage entities are nice, but need more power. This should support secondary indexes (when those are added) and also partitions with mixed schema rows.
Need to support all of this http://docs.amazonwebservices.com/AmazonSimpleDB/2009-04-15/DeveloperGuide/UsingSelect.html
Thanks for the request! We have delivered support for projection (select), which you can read about at http://blogs.msdn.com/b/windowsazurestorage/archive/2011/09/15/windows-azure-tables-introducing-upsert-and-query-projection.aspx (along with two extra Update options), allowing you to specify which properties you want included when querying tables. The other features requests are under review.
Microsoft says: Azure Table Storage is very good ,
Microsoft says: Azure Table Storage don't support (count, skip) operation,
And Microsot kidding us.
no skip, no count = no paging,
no paging = no good choice, no good datastorage
geronimo was here.
Alexsandro Pereira commented
Oh please release these features, I'm monitore this post by one year old =/ I need too much .Contains feature.
Atabong Fombon commented
Please add these features.
So... 4 years later. Where are we with Count, Distinct, Contains? Has there been any news at all about Table Storage lately?
Please add Distinct() as well!!
Stephen Durden commented
Please support Count(). I need it.
Somehow I ended up back here while searching for using count with linq, and forgot that it wasn't supported. I also see nobody from Microsoft has replied since my last comment in August...great.
Please add sorting/orderby to this list as well. I didn't know table storage was so limited until I started trying to do something with it. :(
Alexsandro Pereira commented
Give me contains feature or give a mongodb engine :)
James Reategui commented
I would either discontinue the Table Storage because it gives the overall product a bad rep, OR make the improvements.
I know it would cannibalize some of the more expensive SQL Azure sales, if they added too many more LINQ features.
Jamison Morrow commented
Thanks to basic limitations like these, I'm having the worst time finding a use case for Azure tables that doesn't multiply my dev time, performance, and total lines of code by a factor of 5. I've given them a chance more than once. I've discovered I like the "idea" of Azure tables far more than the actual implementation. I've been forced to revert to SQL Azure each time out of necessity.
Still waiting for this feature guys! It's been over 2 years now. :) I'm specifically waiting for the ability to perform Counts.
Marc Kuperstein commented
I thought I heard that Count() was planned. Am I looking at the correct item?
Awesome idea ;)
Select was provided back in Sept 2011, so there has been some progress
Is this ever going to be implemented. It seems like the table storage development has stopped on Azure. It has been 2 years since this was suggested. Also same for Text search on table storage. Can we at least get a "NEVER GONNA HAPPEN" so we can quit holding out hope?
Oliver Weichhold commented
Almost looks like further development of Azure Tables is completely dead.
Need atleast orderby based on column for top operator. The current set are like iron age API's. Please understand the developor challenges.