You're prompted to save the file, you can choose to change the default extension from .SQL to .PLS if you want.
Hi Jeff, sure I know that but why the arbitrary change - we got used to those defaults and now they change randomly ? Or is there some preference I missed (then it definitely was not migrated from 3.x)
1 person found this helpful
Having the 2 database objects in a single file, a PLS, would 'break' the procedure editor if you were to open it in SQL Developer. I'm guessing that's why we changed it. So it would open in a worksheet where you could run it as a script to have both objects created.
Alright, makes sense, as a matter of fact I often cut and paste from a .pls to a worksheet, then hit <F5>.
But there may be people who have put .pls files under versioning, and the change of convention would be annoying to them.