Discussions
Categories
- 197.1K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.7K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 555 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.3K SQL Developer
- 296.3K Development
- 17 Developer Projects
- 139 Programming Languages
- 293K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 158 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 468 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
New Release: 19.3.3. Lots of features! Try it out and let us know what you think
Comments
-
Hi, no it is not available in 19.3.3.
This is scheduled for the next release.
-
Thanks alot for the nice comments and for taking the time to give us your feedback!
*We plan to add Materialized Views in the next release. Are there other objects types that are missing that you think are critical?
*Intellisense for aliases is also a strong possibility for the next release
*Intellisense is pretty fast, so you may be suffering from the latency you described because your network is slow. Are you experiencing intellisense slowness for any object type, or just some of them? For your own users schema, or others? We already prioritize your schema and commonly used objects but perhaps we could add a way to prioritize other schemas. Could you give more detail on what is slow for you?
*We do plan to add PL/SQL debugging in a future release
Thanks again!
-
Hi, our extension does not provide a way to modify the colors used for highlighting.
But please press F1 and in the command pallete type "theme". There you will see choices for color themes as well as a way to create your own custom theme. It may be possible that you are able to get things the way you like. Once you have tried that, let me know how it goes.
As for the issue with the results window showing one less row, we are aware of that. It seems to happen most when the Page Size extension setting is set to a lower number. Can you try setting Page Size to 20+?
-
Christian, thank you for collecting it and also just the updates in general I know we're talking enhancements but what you've done already is great. For your questions:
<<Are there other objects types that are missing that you think are critical?>>
I think for most workflows all that is missing are Materialized Views. It may be nice to add something like the public DB links that your user can see within your own schema but its really not as needed as materialized views. Maybe it is my work environment but we utilize them A TON.
<<Are you experiencing intellisense slowness for any object type, or just some of them? For your own users schema, or others? Could you give more detail on what is slow for you?>>
It is the second scenario. Things in my schema are fine but others pull up when you detect we are using them. So if I log in as GREG but plan on working on a package against schema BOB, BOB only starts populating when I first type into it. If it is a particularly large schema I could be waiting a bit for BOB to get pulled in. It would be nice to have a box or setting per connection that says pull in the data for these schemas upon connection so that can get out of the way up front. If it also und
-
Hi... I have set the Page Size to 25, but this hasn't helped. Hopefully it will be resolved in the next iteration. I've attached a quick snapshot of both the size issue and the colouring. I wasn't able to find anything in the theme. But I'm not familiar with what the setting might be called.
Greatly appreciated and really like using this tool. Thanks!!
-
Hi there,
Great extension, I have a couple of questions and suggestions for next version:
- Is it possible to check the compilation errors? After a package compilation a have to execute "SHOW ERRORS" to check whats wrong with the code.
- The extension supports vs code symbols or is planned this feature? This is really useful especially when the package is big.
- The intellisense is fantastic, it would be great if we have the option to auto complete in lower case.
- A better option to search an object. My database is really big, and search an object by schema and typing name in herarchy is really annoying. In SQL developer is so simple, just select the object name in the editor and press Shift+F4.
Sorry about my English, i speak Spanish :)
-
Thanks and sorry you are hitting this. Hopefully we can fix this in the next release. Sometimes I don't see this issue, but I have not isolated why it works sometimes and not others. Thanks again for the report.
-
Hi is the issue the thin results table or the color scheme? I can confirm and try to get a capture of the small results area if that is the issue i have noticed it as well.
-
Hi, I very much appreciate the work put into improving this extension. Once the "Other Users" feature was added to browse other schemas I have been able to use this extension in my regular SQL workflow. I love the extension overall.
However, one issue I am having is that the last row of the table preview is cut off. Below is a result with just two rows to show the effect:
This is just slightly annoying when trying to read off an aggregation, because I have to scroll to see the last line. Not a big deal once, but if I'm reading off ten or more aggregations it becomes a little more cumbersome (e.g. if I am entering the numbers into a form I have to keep switching windows). I know it is a small thing but it would be an improvement. (Sorry if it was mentioned above, I haven't read through previous posts).
My only other feature request would be a whitespace formatting feature (as in SQL Developer when hitting ctrl+F7).
-
- Compilation errors can be seen (without using SHOW ERRORS) if you edit PL/SQL using "Edit" option in Oracle Explorer. It is currently not available for other SQL scripts. We are looking into that for a future enhancement.
- We are planning to include breadcrumbs soon, hopefully in the next release to make it easy to navigate though a large PL/SQL package.
- Interesting suggestion. I will let the team know.
- We are trying to improve performance in large databases
Thanks for the valuable input!
Christian
