When
Project Raptor finally came to fruition as a download in
mid 2007 as
SQL Developer 1.2, I was excited at the prospect of having a free GUI that I could take with me to various clients, without worrying about licensing.
I was using
PL/SQL Developer at the time which was great for the PL/SQL development I was doing. I still use
SQL*Plus fairly regularly as a lightweight tool, put as OraFAQ suggests,
SQL Developer was intended as a complimentary tool.
I've heard a few comments recently saying how flakey and unreliable
SQL Developer is. After further questioning, it appears they are referring to the 1.2 version which I will admit, was obviously an entry-level product. v1.5 was the better stable release before 2.x came out.
I'm currently using the most recent patched release (2.1.1.64), and I'm fairly happy although I still have a few gripes.
What made me think of this was an e-mail from a colleague now working in the UK, here are my extended responses:
I started a new contract this week and have been trying to use SQL Developer again, but it doesn't always do things I expect. They are using some cross database tool called DBArtisan (Sybase background) and I'm not impressed with it.
It's always good to get feedback on tools from other databases - interesting.
So far there are 2 things I haven't worked out. The first is multi-session/threads, is this possible?
Most of the time I work with one connection for each schema/database that I happen to be working on. This means that any DML is reflected in all views of that information - on the worksheet, the table data view etc.
If you define a new named connection for the same schema, then you have started a separate session that will not see your uncommitted DML.
The second is that there code base is not exactly formatted very nice so I wanted to try auto-format it. I end up with line breaks where i don't expect, not enough white space and it doesn't seem to allow you to set the case on anything other than keywords, rather frustrating.
I've been thinking about this, and I think it just boils down to personal style. An evolving formatting tool couldn't possibly cater for everybody, and I know our styles are similar. I remember the formatter for
PL/SQL Developer &
Toad being very effective - but they're more mature products. That being said, I don't really use auto-formatters. In fact, I still do most of my PL/SQL development using
TextPad. I use SQL Developer mainly for ad hoc SQL queries and looking at table definitions.
Any advice you can give me on how I might achieve this in SQL Developer. I will admit that what it does with statements when you are grouping by adding to the group by clause is pretty cool, it surprised me today when it appeared in something I was writing
This is what I told him about that one: As for completion insight - I have all those options turned off, first preferences I change on a new pc, that and line numbers in the gutter & NLS date parameter to include century.
There are a couple of other comments I let fly in my reply, things I felt compelled to address.
Error reporting is a real pain in the behind. If you're just tweaking things, yeah, it works - but iterative development, I still compile my PL/SQL in SQL*Plus - my edits direct from Textpad. The error reporting is much clearer.
Unless I'm using it wrong, I don't find compiling code in SQL Developer helpful at all.
It's JRE based
It just makes things slower, introduces lag which grinds my gears. Now I may be pinning the tail on the wrong donkey, but all the other non JRE products I use don't have these issues. That, and it consistently leaves a 500mb footprint in my laptop's memory. However I know this will never change - tweaks in its guts may improve efficiency, but it will always be JRE based. I will say a clear advantage here is you don't need to "install" it, copy the files onto your OS and you're ready to go. Super!
Best I conclude my rant for now. Did I miss anything?
ScottWe
ps - commendations to
Sue Harper,
Kris Rice and the rest of the
SQL Developer team - the product has come a long way in the past half-decade. People always have something to complain about :-)