Using the TableSet class with a predefined Entity I ran a Linq query, which resulted in a bad request. When I viewed the request/response in Fiddler I ran into strange behavior:
Where CreateDate is a DateTime? and mindate is a valid DateTime.
CreateDay and current/prev/nextPartition are both strings as well as processName. _table is the TableSet in this case. The Entity is strongly typed and the columns are all available in storage.
The request sent by the application was (URL decoded):
$filter=CreateDate gt datetime'2014-04-29T12:12:49.5952511Z' and ProcessName eq 'xxxxxxxxxxx') and ((PartitionKey eq '2014042912' or PartitionKey eq '2014042913') or PartitionKey eq '2014042911'
Naturally this resulted in a bad request. While running the query manually with the closing bracket after [ProcessName eq 'xxxxxxxxxxx'] moved to the end of the query resulted in a 200.
Using the TableSet class with a predefined Entity I ran a Linq query, which resulted in a bad request. When I viewed the request/response in Fiddler I ran into strange behavior:
The Linq Query was:
Where CreateDate is a DateTime? and mindate is a valid DateTime. CreateDay and current/prev/nextPartition are both strings as well as processName. _table is the TableSet in this case. The Entity is strongly typed and the columns are all available in storage.
The request sent by the application was (URL decoded):
Naturally this resulted in a bad request. While running the query manually with the closing bracket after [ProcessName eq 'xxxxxxxxxxx'] moved to the end of the query resulted in a 200.
Rewriting the query to
did the job, but retrieves a bigger set from the server than needed.