什么是PL/SQL开发的理想工具箱? [英] What is the perfect toolbox for PL/SQL development?

查看:68
本文介绍了什么是PL/SQL开发的理想工具箱?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

几个月以来,我从事两个项目,这些项目具有大量PL/SQL代码.

I work on two projects with a lot of PL/SQL code since few months.

但是,我没有找到任何真正有趣的工具来开发这种语言.

However, I didn't find any really interesting tools to develop on this langage.

目前,我的配置包括以下工具:

For the moment, my configuration includes the following tools:

  • Eclipse (该应用程序的其余部分是用Java开发的),其 PsPad 用于编辑我的PL/SQL文件.
  • SQL Developer (我也有TOAD,但我不太了解/喜欢这个工具).
  • Eclipse (the rest of the application is developed in Java), with PL/SQL Editor plugin
  • As I really don't like and trust the PL/SQL Editor plugin for Eclipse, I use mainly PsPad for editing my PL/SQL files.
  • SQL Developer (I have also TOAD, but I don't really know/like this tool).

那么,用于开发PL/SQL应用程序的完美"工具箱是什么?

So what is your "perfect" toolbox for developing PL/SQL applications?

我还阅读了SQL Developer 2.1引入的PL/SQL单元测试功能.是否有人对此功能和此版本的SQL Developer(我仍使用1.5)有任何反馈?

I've also read that SQL Developer 2.1 introduces a PL/SQL unit testing feature. Does anybody has a feedback about this feature and this version of SQL Developer (I still use 1.5) ?

推荐答案

作为一种老式的小伙子,我仍然主要还是与SQL * Plus和 Subversion .

Being an old-fashioned sort of chap I still mainly get along with SQL*Plus and the TextPad IDE. TextPad is nagware, but the licence is cheap and the tool has some fantastic features. Also people have written PLSQL syntax libraries for it, which give you keyword highlighting. It is also possible to hook TextPad into other desktop tools such as Subversion.

SQL ^ Developer用Java编写,这意味着它是内存的虚耗者.拥有数据浏览器无疑还有优点.即将发布的2.1版本还具有内置单元测试,可能会很好吃.

SQL^Developer is written in java, which means it is a voracious consumer of memory. Still there is undoubted merit in having a data browser. Also the upcoming version 2.1 features built-in unit test, which could be very tasty.

有用的实用程序:

  • pldoc ::生成Javadoc样式 注释中的文档 您的包裹规格
  • utplplsql ::单元测试工具; 旧的,但仍然可以使用
  • QUTO ::另一个更多 复杂的单元测试工具 (我不使用相同的 我仍然与之共处的原因 SQL * Plus和TextPad)
  • QGCU :: PL/SQL代码生成器 (以前是QNXO)
  • pldoc :: generate Javadoc-style documentation from the comments in your package spec
  • utplplsql :: unit test harness; old but it still works
  • QUTO :: another, more sophisticated unit test harness (which I don't use for the same reason I'm still hacking with SQL*Plus and TextPad)
  • QGCU :: PL/SQL code generator (previously QNXO)

捍卫Luddism

TOAD和SQL * Developer之类的工具的危险在于,它们使我们无法直接对数据库执行DML和DDL,包括编辑PL/SQL源代码.按照完成工作"的精神,这很好而且花花公子.直到我们需要还原更改为止.或生产DBA需要脚本....

The danger with tools like TOAD and SQL*Developer is that they allow us to execute DML and DDL directly against the database, including editing PL/SQL source. This is fine and dandy and awfully in the spirit of Getting Things Done. Until we need to revert our changes. Or the production DBA demands a script....

当然,可以以安全的方式使用TOAD或SQL Developer-我知道SQL Developer也可以加入源代码控制-如果只需要更多的自律性.

Of course it is possible to use TOAD or SQL Developer in a safe fashion - I know SQL Developer can hook into source control as well - if just requires more self-discipline.

这篇关于什么是PL/SQL开发的理想工具箱?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆