更新 Oracle 数据库中的包体（Sql 开发人员）
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/20745759/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
update the package body in Oracle Database (Sql developer)
提问by Eric Cheung
I need to have a miner update to the package body in Oracle Database using Oracle SQL Deverloper 3.2. The update does not need to change the package specification.
我需要使用 Oracle SQL Deverloper 3.2 对 Oracle 数据库中的包主体进行矿工更新。更新不需要更改包规范。
Using the Oracle SQL Deverloper, I right-click on the package name, choose "edit body", then update the body.
使用 Oracle SQL Deverloper，我右键单击包名称，选择“编辑正文”，然后更新正文。
Then I find that it seems there are several ways to update the package body:
然后我发现更新包体好像有几种方法：
(1) click "run" button.
(1) 单击“运行”按钮。
(2) click "compile" button.
(2) 单击“编译”按钮。
(3) click "compile with debug" button.
(3)点击“编译与调试”按钮。
(4) close the tab of package windows, then choose "yes" to save the changes on the pop-up windows.
(4) 关闭包窗口选项卡，然后在弹出窗口中选择“是”保存更改。
My questions are:
我的问题是：
1) what are the difference in the above 4 ways?
1）以上4种方式有什么区别？
2) which is the proper way?
2）哪个是正确的方法？
Thanks a lot
非常感谢
Regards
问候
回答by Maheswaran Ravisankar
1) When you click "Run", the SQL Developer starts to execute the current Active SQL. And now it is a CREATE OR REPLACE PROCEDURE..., so it turns to be a DDL
1) 当您点击“运行”时，SQL Developer 开始执行当前的 Active SQL。现在它是一个CREATE OR REPLACE PROCEDURE...，所以它变成了一个 DDL
2) When you click Compile, Developer explicitly do the same as previous. No difference actually.
2) 当您单击编译时，Developer 显式执行与之前相同的操作。其实没什么区别。
3) When you choose for Debug, if you enable "debugger" in SQL Developer, then you can enable breakpoints in your code, after compiling.
3）当你选择Debug时，如果你在SQL Developer中启用了“调试器”，那么你可以在编译后在你的代码中启用断点。
4) When you click Save, SQL Developer simply pushes the code to be Executed, again as Step1.
4) 当您单击保存时，SQL Developer 只是推送要执行的代码，再次作为 Step1。
All are proper ways, but when you SQL developer to edit your proc, you may feel some slowness, because it do maintain some persistent setting behind the screens, and it is slightly buggy. It wont harm, but just slows down.
都是正确的方法，但是当您的 SQL 开发人员编辑您的 proc 时，您可能会感到有些缓慢，因为它确实在屏幕后面维护了一些持久设置，并且它有点错误。它不会伤害，但会减慢速度。
