Compiling "bugs" in SQL Developer 4.0.0.12

Question

Has anyone came across a bug in SQL Developer where on compiling a trigger, it moves around lines of code/sql causing the trigger to compile with errors?

For example, I made a change to a trigger last night and hit compile. It came back with an error saying that I was missing an End If at the end of the trigger. It had removed two END IFS from an IF statement I had further down in my trigger.

I amended this and compiled it again, this time successfully. However, I found out this morning that it had moved around my INSERT INTO ordering!

For example, I had:

insert into table(
A, B, C, D,
E, F, G, H,
I, J, K, L,
M, N, O, P)
VALUES (
A, B, C, D,
E, F, G, H,
I, J, K, L,
M, N, O, P
)

After I compiled it became:

insert into table(
A, B, C, D,
E, F, G, H,
I, J, K, L,
M, N, O, P)
VALUES (
E, F, G, H,
I, J, K, L,
A, B, C, D,
M, N, O, P
)

Which meant it compiled without any issues but running it caused values to go into the wrong columns and eventually an error when a max length was breached.

Answer 1

4.0.0.12 was the second early adopter release - a beta, in other words - and was released in September 2013. There was a third EA release, and there have been three production releases so far since December.

The current version at the time of writing is 4.0.2 (4.0.2.15). Unless you have a pressing reason to stick to the early adopter/beta version you should probably just upgrade to the production version.

I can't immediately see anything relevant on the SQL Developer forum, which is where early adopter issues were supposed to be reported. That doesn't mean it wasn't reported, or spotted internally, and fixed. I doubt they'd be very interested in this now if it has already been fixed in a later version, though.

If you upgrade and do still see this or any other bugs then the release notes say to report them on My Oracle Support.