Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Document that utPLSQL does not make use of any costed database options #1064

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
john-otoole opened this issue Mar 27, 2020 · 1 comment · Fixed by #1065
Closed

Document that utPLSQL does not make use of any costed database options #1064

john-otoole opened this issue Mar 27, 2020 · 1 comment · Fixed by #1065
Assignees
@jgebal
Labels
documentation
Milestone
v3.1.11

Comments

@john-otoole
Copy link
Contributor

john-otoole commented Mar 27, 2020 •
edited
Loading

While installing utPLSQL v3.1.10 on a customer's development database recently, we were asked by the customer's DBA team if utPLSQL is using any licensed Oracle database features such as Diagnostics pack / Tuning pack. They saw that it is using DBMS_PROFILER and wondered what else it might be doing. I know that utPLSQL is not using Diagnostics pack / Tuning pack and that it uses DBMS_PROFILER for code coverage. I responded to them with that information.

Would it be worth stating some of this in the utPLSQL documentation? e.g. on the install.html page of the documentation, explicitly state that utPLSQL does not have any dependency on costed database options such as Diagnostics pack / Tuning pack / Partitioning etc.
@PhilippSalvisberg
Copy link
Member

PhilippSalvisberg commented Mar 27, 2020 •
edited
Loading

Thanks for reporting this.

The installation part of the documentation states that

utPLSQL may be installed on any supported version of Oracle Database

So the answer is, that it does not use features of Oracle Editions that must be licensed separately.

However, I guess we could add that to the documentation for clarification purposes.

@jgebal jgebal added this to the 3.1.11 milestone Mar 29, 2020
@jgebal jgebal self-assigned this Mar 29, 2020
jgebal added a commit that referenced this issue Mar 29, 2020
@jgebal
Added explicit requirements
83ee513 
Resolves #1064

updated invite link for slack as the herokuapp invite solution doesn't since quite some time and Slack has it's own invite links now.
@jgebal jgebal mentioned this issue Mar 29, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jgebal jgebal

Labels
documentation
Projects
None yet
Milestone
v3.1.11
Development

Successfully merging a pull request may close this issue.

Added explicit requirements utPLSQL/utPLSQL
3 participants
@jgebal @john-otoole @PhilippSalvisberg