如何从oracle数据库中获取对象的副本
我计划发布我们的产品。我们正在使用 Oracle 表单来开发我们的软件。
所以我有两种类型的对象用于发布
- Front-end =>; Oracle表单
- 后端=> Oracle 数据库程序(过程、函数和包)
发布的重要部分之一是我们需要备份,以便在发生任何情况时我们可以使用旧版本。
顺便说一句,对于前端对象,我将使用一些批处理文件来为前端对象创建备份,但对于后端对象,我不知道如何获取函数、过程或包的副本(规范和主体) ) 自动地。
知道我怎样才能自动完成它吗?请给我建议。 我们正在使用 Oracle 10g & 9i
I have plan to do a release for our product. we are using Oracle forms to develop our software.
So I have two type of object for release
- Front-end => Oracle forms
- Back-end => Oracle Database Program (Procedure, function and Package)
One of the important part of release is we need to have a back up so if any thing happen we can use the older version.
By the way, for front end object I will use some batch file to create a back up for my front end objects but for Back-end object I dont know how I can get a copy of function, procedure or package(spec & body) automatically.
Any idea how I can do it automatically? please advice me.
we are using oracle 10g & 9i
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
在存储库中存储代码有什么意义?测试配置有什么意义?发布管理有什么意义?
如果这些捣乱客户生产环境的牛仔开发人员是您需要的员工强制执行流程以确保仅部署经过认证的配置,如果需要进行紧急调整,则应将这些
配置改装到正式版本中,那么我想您无法阻止它们。不必支持他们,而你不必对他们的变化负责(除非销售合同规定你必须这样做,这不会让我感到惊讶。)
So what is the point of storing code in a repository? What is the point of testing a configuration? What is the point of release management?
If these cowboy developers who muck around with your customers' production environments are your staff you need to discipline them. Enforce process to guarantee that only certified configurations are deployed. If emergency tweaks are required these should be retrofitted into the official build.
If these developers actually work for the customer, then I suppose you cannot stop them. But you don't have to support them, and you don't have to be responsible for their changes. (unless the sales contract says you have to, which wouldn't surprise me.)
(对代码块表示歉意)。
以下是我用来处理此类问题的一些代码:
我建议将这些过程放入一个包中。调用 DUMP_OBJECT 获取您想要转储的内容。
分享并享受。
(Apologies for the code-blob).
Here's some code I've used to handle issues like this:
I suggest putting these procedures into a package. Call DUMP_OBJECT for the things you want dumped.
Share and enjoy.