Recent content by William Robertson

Two spaces never seemed enough for PL/SQL in my opinion, as SQL itself has a lot of indents which are more than two spaces, so you often don't get a clear visual block with less than four. I find formatters in general always end up being frustrating, as there will be rules that don't quite work...

This would be a nice feature, as typically - especially for partitions - the PCTFREE, INITRANS etc settings are simply the system defaults. For a table with a lot of subpartitions these can add megabytes worth of useless junk to a generated DDL script.

Also, keeping when/then on the same line would also save me a lot of manual editing: case when xxx then 1 when yyy then 2 when zzz then 3 else 4 end

It sounds as though compiling your procedures in the Command window has failed somehow. If you view the database source, is the new version or the old version in the database? I don't think your issue is related to the Test window. In 20 years of using PL/SQL Developer, I have never tried...

I'm curious about your workflow. You edit your source file in a program window, but you can't see the change you just made? I don't understand. Or are you saying you made the change in another editor such as Notepad++ and the program window is not automatically refreshing?

Can you try mapping them explicitly in the Key Configuration preferences page? Find Edit / Clipboard / Cut and set the key as Ctrl-X, and so on.

I agree that you should have the choice, and unexpected changes complicate change history and pull requests etc, but not having a space there seems a rather odd preference to me. Normally you would have no space between a function and its arguments, like nvl(somevalue, 0) and not nvl...

I'm curious how you would execute a PL/SQL block in a Program window. That's what Test Windows are for, isn't it?

The same thing happens in SQL*Plus, so I don't think it's a PL/SQL Dev issue. The default value is stored as a string so a conversion to numeric is required at insert time anyway, but maybe the stray CRLF requires an extra processing step that could show up at high volumes. Maybe someone less...

Not a solution, but rather than killing via Task Manager you can often cancel the currently executing call from another window (or another instance of PL/SQL Dev if running in dual session mode - or SQL*Plus of course but you need to find the sid/serial you want to cancel). This at least...

No, they seem to have the issue in the select list. Maybe they are just doing it wrong somehow. I'll see if I can try it myself on their PC, though it's not always possible when you are screen-sharing remotely.

I’m not sure how I would do that, as it would just be the same scenario but they can only pick one item off the list where I can pick multiple items, using the same version of PL/SQL Developer (12, though lucky colleagues in another office have 15 but the same issue) and Windows 10. I was just...

For example, if I start typing a query like select s. from user_sequences s so that Code Assistant pops up a list of columns to expand "s." I have noticed colleagues painstakingly selecting one item at a time, but when I suggest using control-click to select multiple items, it only lets...

In PL/SQL Developer 12, I can select multiple items from lists using control-click, but this doesn't seem to work for some of my colleagues. Is there some setting that could affect this? I've looked but I can't see anything likely, and I'm not sure why there would be a preference setting for it...

I notice Plyxon defaults to the legacy Courier New as its editor font. Can I suggest instead defaulting to Consolas on Windows, or shipping with Fira Code, to give it a cleaner and more modern look. (I see it supports ligatures - nice!)