SimpleDB select API and QueryExpressions

hi,

We are having a bit of trouble with QueryExpressions and predicates with the fancy new SimpleDB Select API Changes.

 basically, building QueryExpressions does not seem to be putting parenthesis in the logical places.

 for example:

--------------------------------

var queryExpression =
                (Entity.Attribute(Fruit.ExpiresOnField) >= DateTime.UtcNow && Entity.Attribute(Fruit.CreatedOnField) >= oldestDate)
                && (Entity.Attribute(Fruit.TypeField) == typeof(Apple).Name || Entity.Attribute(Fruit.TypeField) == typeof(Pear).Name);

------------------------------

creates a simpleDB call like this:

-------------------------------

Action=Select&SelectExpression=SELECT
CreatedOn, DeletedOn, Description, ExpiresOn, Title, Type, UpdatedOn
FROM Fruit
WHERE
(ExpiresOn >= '2009-09-10T20:55:40.656' AND CreatedOn >= '2009-06-10T15:55:38.717' AND Type = 'Apple' OR Type = 'Pear' AND DeletedOn IS NULL)
ORDER BY CreatedOn  desc

LIMIT 20 

---------------------------------

since there is no parenthesis around the Type predicates, it results in this simpleDB error:

------------------------------------

<?xml version="1.0"?>
<Response><Errors><Error><Code>InvalidSortExpression</Code><Message>Invalid sort expression. The sort attribute must be present in at least one of the predicates, and the predicate cannot contain the is null operator.</Message><BoxUsage>0.0000137200</BoxUsage></Error></Errors><RequestID>9a4e5014-1392-149e-67c3-184bb75a38a0</RequestID></Response>

----------------------------

 Rather, we would like the QueryExpression to create something like this:

---------------------------

Action=Select&SelectExpression=SELECT
CreatedOn, DeletedOn, Description, ExpiresOn, Title, Type, UpdatedOn
FROM Fruit
WHERE
(ExpiresOn >= '2009-09-10T20:55:40.656' AND CreatedOn >= '2009-06-10T15:55:38.717') AND (Type = 'Apple' OR Type = 'Pear') AND ( DeletedOn IS NULL )
ORDER BY CreatedOn  desc

LIMIT 20  

------------------------------

Are we formatting this QueryExpression incorrectly? or maybe this is already fixed with a more recent build?

We are still using the build from 9/10

Thanks,

-joe Freeman

 (commie mutant traitor)

 

Your query expression is fine -- we were not adding enough brackets when emitting the SELECT expression.  This will be fixed in the 18 Sept nightly build -- please let us know if you still see issues.

And please accept our apologies that this has taken a while to turn around -- we have all been tied up with a conference for the last few days.

Not a problem.. Any thoughts on my maxnumberofitems post? Hope the conference was good... Thanks, -Joe

Yes, we've reproduced the problem (unfortunately our test for multi-request loading was for 300 items, which caught the issue in Query, but didn't trigger the limit in Select), and I'm working on it -- will post on the other thread when we have a fix, hopefully later today!