If you have suspected bugs to report or enhancement requests please report them to Oracle using the sql developer exchange.
This forum is to help people with problems they have USING the product. There aren't any 'workarounds' for what you report.
The quotes are intentional..side effect of allowing users to drag and drop strings from a grid to build a quoted string list for a WHERE X IN (...) clause
You'll need to use search/replace to remove the quotes for your use case
On the timings, see the View - Log - Statements panel and observe any SQL taking too long..and compare to 18.1
Thank you Jeff.
The timings of the statements are fine in 18.2. The statements executed even faster than on 18.1, you can see it on the screenshots attached.
The timings on 18.1
The timings on 18.2
If the elapsed time is in ms, then in any case it is negligible compared to the response time of SQL Developer itself.
Regarding the quotes, is there a way to construct Insert statement right in the editor from the table name ? This drag and drop from popup describe was very useful for it. Now, unfortunately, it requires more effort.
>Regarding the quotes, is there a way to construct Insert statement right in the editor from the table name ?
Just type your insert, and after the (, the pop-up will come up. It lets yo select one or more columns. and will place them in the editor IN THE ORDER in which you click them.
It should be even faster than open a DESC popup and dragging and dropping.
It's opening pretty much in less than a second for me, in both my 18.2 and 18.3 development build.
Tell me about your table, does it say...have 800 columns? Or some custom data types?
I'm using HR.EMPLOYEES as a test
Just as a sanity check, I tested Shift-F4 on an empty 1,000 column table (the maximum number of columns supported by Oracle DB (at least as of 11g), with a mix of VARCHAR2 and NUMBER columns). Here are the relevant rows for a first time run on 18.2 from the Statements log:
and another image for a subsequent run in the same 18.2 session:
This is all on a local database connection. The Popup Describe consistently requires about a second, certainly never more than 2 seconds in my environment. Are you connecting to a remote database (either via a LAN or WAN)? I see that even the simple
select UPPER(sys_context('USERENV', 'CURRENT_SCHEMA')) from dual
takes a significant number of milliseconds in your environment.