Sorting a query with an invalid field really slams the query/server

Runs in 0.08 seconds

census.daybreakgames.com/xml/get/eq2/cha...rt=name.first:1

Running the same query but sorting against an invalid field "first" causes times to jump to 30 seconds.

census.daybreakgames.com/xml/get/eq2/cha...&c:sort=first:1

I'd almost rather be told I'm sorting against a field that doesn't exist.

Any thoughts?

Edit-------------------------------------------------------------------------------

Another example of a painful query to sort

census.daybreakgames.com/xml/get/eq2/cha...show=name.first

10 seconds to get 10 results back with no condition statements and only displaying one field is extremely painful.

 

Yeah...this is something that we need to look at in more detail.  More generically, you can cause this by looking for a field that doesn't exist.  For example

/get/eq2/character/?foo=bar

(please don't try this at home)

This is a side effect of haveing such a loose data model.  Hopefully, you won't put these types of queries into your production sites.  Having them be slow when experimenting is okay.

-dan