EA2 export data disappears after error

Question

The export data menu item in the result set context menu disappears after you created an error. E.g. after sending the following statement:
select dummy|| dummy|| dummy|| dummy|| dummy|| dummy from dual;
The call of "export data" raises an error message that the identifier for the column is too long. After that, the menu item "export data" is gone.
Regards,
Sven

Answer 1

Skutz,
Thanks for the response.
Yes, the problem with the export menu option disappearing is fixed with EA3.
As to when the error with the long column names not being able to be exported was previously fixed, I saw the problem (ORA-00972 with the example query given) from versions 1422 through 2579, but not in the subsequent version (2998?) where it was fixed to not cause the error.
On not wanting to rewrite my original base query - SQL Developer is already rewriting it, which is what is causing this problem. I assume the rewrite you are doing simplifies the case where only some of the columns are exported.
My query is, for example:
select dummy|| dummy|| dummy|| dummy|| dummy|| dummy from dual
This runs fine and produces the expected result. SQL Developer's query for exporting is (from what you have said), in that example:
select "DUMMY||DUMMY||DUMMY||DUMMY||DUMMY||DUMMY" from
(select dummy|| dummy|| dummy|| dummy|| dummy|| dummy from dual)
This fails with the "ORA-00972" error, preventing me from using the export functionality for a query that I can run successfully.
I know that the work around is to provide an alias for the column, but the fact that I can apply a work around to my query doesn't change my opinion that it is SQL Developer code that is doing the wrong thing with my query (a bug to me) that is preventing me from being able to us the export functionality for that query.
It is a relatively minor thing, but another example of something that you would expect to work (it certainly does in TOAD) which takes some of the shine off a basically good product.
theFurryOne