Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Cloud Cover Episode 10 - Table Storage API

Download

Right click “Save as…”

  • WMV (WMV Video)
  • MP3 (Audio only)
  • MP4 (iPhone, Android)
  • Mid Quality WMV (Lo-band, Mobile)
Join Ryan and Steve each week as they cover the Microsoft cloud. You can follow and interact with the show at @cloudcovershow

In this episode:

  • Learn about the Table storage model - PartitionKeys, RowKeys, and more.
  • Walk around the API using the StorageClient library and learn how to query the service without first building a data model.
  • Hear the latest news and announcements for the platform.
  • Troubleshoot a common query error when using Table storage. 

Show Links:

Windows Azure Guidance - Failure Recovery (via Eugenio)
SELECT INTO with SQL Azure
Application Infrastructure Virtual Learning
Windows Azure Firestarter videos
Protecting Blobs from Application Errors
Protecting Tables from Application Errors
Table Storage Backup and Restore on CodePlex

Tags:

Follow the Discussion

  • The biggest issue I have with Azure Table Storage is the lack of string comparison operators.

    If I can do
    .Where(a=>a.Age > 21)

    and

    .Where(a=>a.Name.CompareTo("Dave"))

    then why can't I do

    .Where(a=>a.Name.ToLower().Contains("dave"))

    Is this an architectural constraint or rather an implementation limitation?

    If it's an implementation limitation, then I can hope that it will be fixed in a future release.

    If it's architectural, then I will have to find an alternative solution such as SQL Azure.

  • Hi DaveSn,

     

    Currently, this is a limitation in the actual storage service.  The LINQ provider eventually boils down to a URI with some syntax that is or isn't supported on the service head.  It turns out that certain operations that are supported in relational sources are not supported in Windows Azure tables.  Your specific question would entail a full-text search to be performed on an arbitrary column in Windows Azure.  This is not currently supported (there is no LIKE operation).  This limit might be removed over time as more features are added to the service.

     

    If you really need full text search capability over your data - take a look at the Lucene implementation here:

     

    http://code.msdn.microsoft.com/AzureDirectory

     

Remove this comment

Remove this thread

close

Comments Closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.