Binary protocol error with incorrect fetchplan [moved]

[lvca]

This is Issue 309 moved from a Google Code project.
Added by 2011-04-20T14:09:47.000Z by Anton.A....@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Closed (Fixed).

Original labels: Type-Defect, Priority-Medium, v1.0rc2

Original description

<b>What steps will reproduce the problem?</b>
1. Call to recordLoad with correct RID and incorrect fetchplan, e.g. &quot;INVALID&quot;
2. Read request status = 0, all is going well, read transatcionID...
3. First record will return its status as 1 = is a part of result set
4. Read first record
5. Read next record status, which is 1 (but this is not a record-status, this is a overall response status instead)


<b>What is the expected output? What do you see instead?</b>
Maybe OrientDB should check fetchplan syntax before outputting first record?
Command() query with invalid fetchplan returns 1 as request status, therefore its calls are correct. 

<b>Please use labels and text to provide additional information.</b>
1.0-rc1 r2688