Developing SQL scripts, PLSD vs. SQLNav

[BMarcus926]

I'm very pleased with my switch from SQL Nav to PL/SQL Dev, except for one thing, really, that might prevent me from doing so. When developing SQL scripts on SQL Navigator, I can use either ";" or "/", just like SQL Plus, AND I can single step very easily. In the PLSD Command Window, single-stepping seems to lock up the script to where I can't make changes, or go back to a prior step, etc. In the SQL window, I can't use "/", which is how I've always run an anonymous block terminated with ";", for example. Is anyone well-versed in SQL Nav that knows what I'm talking about, and can tell me how to do the same stuff in PLSD?

 

[ScottMattes]

The SQL window has a setting (called Autoselect I think) that will select the SQL command that the cursor is on and execute it. You can manually select a command and execute it too.

The Test window is for stepping through code and so far I haven't had any big issues with that.

------------------
------------
Scott Mattes

 

[BMarcus926]

I did toggle the "autoselect" feature you mention, but the SQL window does not advance to the next statement -- sounds trivial, perhaps, but is highly annoying. Also, unless I'm missing something, "/" is not acceptable, which creates a problem for the large number of scripts I have in development.

The Test window doesn't allow single-stepping that I can see, and cannot open an existing SQL script, and also doesn't allow "/".

One other thing while I'm on a roll: SQL Nav will let you batch-run a series of SELECTs, opening a series of grids, accessed by tabs, one for each SELECT. This capability would be great, although not critical.

The reason I bring up these points is only because I think PLSD is a strong product, with a better code base and a better interface than the much more costly SQLNav. It's just this one area that is frustrating. Perhaps it's because PLSD is more geared towards strictly PL/SQL development ... but in my experience writing useful PL/SQL, especially in the Data Warehouse/ETL world in which I live, goes hand in hand with developing, testing, and running lots of supporting SQL scripts.

 

[mike]

I don't write a lot of scripts, but I've used the / in the command window editor and I think it works OK.

I use the command window for scripts like you were doing and have the script in the editor tab. Pressing the pause button on the status bar at the bottom is similar to setting pause on in SQL Plus. When you press the execute icon (F8), it will pause at the first / or ; in the script and highlight the code in the editor tab. Pressing the run button on the status bar on the bottom will execute the next statement. If you need to edit your code, while doing this, hit the lighning bolt to quit, edit the code in the editor tab and then start over. It doesn't seem nearly as sophisticated as the debugger used for packages, but you can step through your code. If you want your code to just run all the way through, make sure that the pause button is unselected.

As far as multiple SQL statements, you can have several statements in the command window separated by a "/" and they will all execute, but they won't be in separate grided windows. You can also turn on the "autoselect" feature mentioned above and put multiple SQL statements in the SQL window delimited by a ";" It won't execute all of them and put them in separate gridded windows like the product mentioned above (At least I've heard - I don't ever use that tool), but you can have several in one SQL window and execute the one that the cursor is on.

Hope that helps.

Mike