Request for UI improvments and some more

Question

Hello Raptor Development Team,
Your product is really good, but there are some obvious UI lacks and some possible improvements (sorry, if these lacks/improvements have been pointed before):
1. There shall be possibility to search a text of a function/procedure/package/... without switching into Edit mode.
2. In SQL*Worksheet by parse error no info is provided in which position in the statement - line, column - error has occurred (even SQL*Plus provides similar info). As far as I can remember it is limitation of error-processing of Oracle JDBC thin driver, but it can quite easily be overcome but re-parsing the same failed statement inside PL/SQL block by means of DBMS_SQL package which provides such info (and it is relatively cheap, as statement has anyway failed on parse).
3. In SQL*Worksheet it should be possible to obtain all properties of an object under cursor by means of hotkey/popup menu (likewise the functionality of F4 button in TOAD) and not only by separate "describe" command (which, anyway, provide quite limited info).
4. Navigation in the left explorer-like panel is quite cumbersome, especially when working with schemas with big amount of objects. It would be nice, if alternative interface (e.g. tabbed a-la TOAD) will be provided. The problem may be alleviated as well by providing in the left panel speedbars that allows to quickly switch between different connections and between DB object types (tables, views, procedures,...) in the same connection.
5. If named bind variable is used in SQL*Worksheet and single statement is executed the "Enter bind value:" dialog box is shown for each bind variable as many times as it occurs in the statement (with empty "Object Value" field and "Object type reset to Varchar2 each time). Looks strange and inconvenient as it provide no clue for which occurrence of the variable value is asked.
6. If the same statement with bind variable(s) is re-executed many times or several statements that refer to same bind variable are sequentially executed in "single-statement" mode that it would be really nice if values will be retained between executions and prompted in "Object Value" field of "Enter bind value:" dialog box.
7. The following PL/SQL block fails
declare
x char(10);
y char(10);
begin
select :a, :b into x,y from dual;
end;
8. This is not directly related to Raptor, but :). Spell-check on this forum does not know following words that shall be very popular here: JDBC, Varchar2, F4 and so on
Yours sincerely,
Oleksandr Alesinskyy

Answer 1

1. Has been mentioned before - we do have a bug on it. To search across all your pl/sql, there is a report you can use.
2. We are working on improving errors but I can't make any promises.
3. We have heard this before but it won't be there for v1.0. You can use the Connections navigator to access the details of the objects that are accessible to you while you have a Worksheet open. You can even drag your Worksheet tab down to place it under the Connections details tab so you can see them both at the same time.
4. In a post-v1.0 release, we will be looking at additional, alternate navigation.
5. We have an open bug to not prompt you for the same bind more than once.
6. I will talk to the Worksheet developer about this one. Not sure we can remember the binds from execution to execution but it would be a great enhancement.
7. Not sure why this is failing - I will check into it.
-- Sharon