Skip to Main Content

SQL Developer

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Formatting PL/SQL in SQLDev 20.2.0 - Unwanted Indentation after Comment - Solution?

Philipp SalvisbergJun 28 2020 — edited Jul 2 2020

When I format the following Code in SQL Developer 20.2

BEGIN

-- a comment

NULL; 

END;

/

I get this the first time:

BEGIN

-- a comment

   NULL; 

END;

/

and this after formatting it the second time:

BEGIN

-- a comment

      NULL; 

END;

/

Every time an additional (unwanted) indentation is added before NULL;. This worked fine with SQL Developer 19.4.0.

Same behaviour with multi-line comments. Same behaviour on macOS and Windows.

Any Idea how I can avoid this additional indentation with SQL Developer 20.2.0?

I hoped we get access to comment nodes in Arbori, based on this thread SQL Developer 19.2.1 - Custom format: line break on hints, columns/argument alignment . But it does not seem so, so I really have no idea how to change formatting when comments are involved.

Thanks

Philipp

P.S.

I use this settings:

sqldev-adv-formatter-settings.png

This post has been answered by Vadim Tropashko-Oracle on Jun 29 2020
Jump to Answer

Comments

bkmcdaniel
Answer
Marked as Answer by 4187794 · Sep 27 2020
InoL

See yesterday's topic (which means if you search before you ask, you will have an answer much quicker):

Oracle Apex Migration(Access to Apex 19.2)

4187794

bkmcdaniel: Thank you for the link!

InoL: I have done a lot of searching. I apologize for not finding that discussion and posting a new thread.

I saw a question on there that I have. Can we stand up an older apex instance to convert applications then migrate those into 19c  - does anyone know how feasible/reliable of an approach this may be?

InoL
Can we stand up an older apex instance to convert applications then migrate those into 19c  -

You can.

However, there is a reason Oracle stopped support: the result was very poor. There is just no way to convert the code to PL/SQL and Javascript automatically. In the end you have to do everything manually anyway.

4187794

Thanks ya, appreciate it.

edit: Even though you have made me sad.

1 - 5

Post Details

Added on Jun 28 2020
7 comments
1,392 views