Skip to content

Improved installation routine #384

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.

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

Merged
merged 11 commits into from
Jul 4, 2017
Merged

Improved installation routine #384

merged 11 commits into from
Jul 4, 2017

Conversation

Pazus
Copy link
Member

@Pazus Pazus commented Jul 3, 2017

addressed #383
addressed #382

@Pazus Pazus added this to the v3.0.2 milestone Jul 3, 2017
@Pazus Pazus self-assigned this Jul 3, 2017
@coveralls
Copy link

Coverage Status

Coverage remained the same at 91.718% when pulling 4dbf6e8 on Pazus:issue-382 into ea2573e on utPLSQL:develop.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 91.718% when pulling 4dbf6e8 on Pazus:issue-382 into ea2573e on utPLSQL:develop.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 91.718% when pulling 4dbf6e8 on Pazus:issue-382 into ea2573e on utPLSQL:develop.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage remained the same at 91.718% when pulling 4dbf6e8 on Pazus:issue-382 into ea2573e on utPLSQL:develop.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 91.718% when pulling 4dbf6e8 on Pazus:issue-382 into ea2573e on utPLSQL:develop.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 91.718% when pulling 3bd33d1 on Pazus:issue-382 into ea2573e on utPLSQL:develop.

1 similar comment
@coveralls
Copy link

coveralls commented Jul 3, 2017

Coverage Status

Coverage remained the same at 91.718% when pulling 3bd33d1 on Pazus:issue-382 into ea2573e on utPLSQL:develop.

Copy link
Member

@jgebal jgebal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you review the proftab comment and also remove the commented code?

@@ -1,4 +1,9 @@
create table plsql_profiler_runs
declare
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm still thinking if we should make scripts rerunable or drop objects on uninstall.
Also, since we modify script provided from Oracle, should we split it into one script per object?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we shouldn't drop it. Could you explain why do you want to split it?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We use a pattern of one script for one object so this script is the only one breaking the pattern

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but its an oracle object, not our... But I can fix it tonight

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, lets leave it as it is

l_tab_exist number;
begin
select count(*) into l_tab_exist from
(select table_name from all_tables where table_name = 'PLSQL_PROFILER_RUNS' and owner in (user,'PUBLIC')
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We cannot have any table with owner = 'PUBLIC'

l_tab_exist number;
begin
select count(*) into l_tab_exist from
(select table_name from all_tables where table_name = 'PLSQL_PROFILER_DATA' and owner in (user,'PUBLIC');
Copy link
Member

@jgebal jgebal Jul 3, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

; at the end.

l_seq_exist number;
begin
select count(*) into l_seq_exist from
(select sequence_name from all_sequences where sequence_name = 'PLSQL_PROFILER_RUNNUMBER' and sequence_owner in (user,'PUBLIC');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

; at the end

jgebal added 2 commits July 3, 2017 17:26
Fixed syntax errors.
Fixed bug when deploying to different user schema
@coveralls
Copy link

Coverage Status

Coverage remained the same at 91.718% when pulling 766af11 on Pazus:issue-382 into 8196046 on utPLSQL:develop.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage remained the same at 91.718% when pulling 766af11 on Pazus:issue-382 into 8196046 on utPLSQL:develop.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 91.718% when pulling 766af11 on Pazus:issue-382 into 8196046 on utPLSQL:develop.

@coveralls
Copy link

coveralls commented Jul 3, 2017

Coverage Status

Coverage remained the same at 91.718% when pulling f97db36 on Pazus:issue-382 into ce2d8ad on utPLSQL:develop.

@coveralls
Copy link

coveralls commented Jul 4, 2017

Coverage Status

Coverage remained the same at 91.718% when pulling 5605837 on Pazus:issue-382 into f92772f on utPLSQL:develop.

@jgebal jgebal merged commit 15a0922 into utPLSQL:develop Jul 4, 2017
@jgebal jgebal removed the in progress label Jul 4, 2017
@Pazus Pazus deleted the issue-382 branch July 15, 2017 09:47
Pazus added a commit that referenced this pull request Jul 18, 2017
### Documentation
  #399 Documentation now refers to [migration](https://github.com/utPLSQL/utPLSQL-v2-v3-migration) project
  #386 Documentation now refers to a valid object name: `ut_file_mapping`
  #362 Install and Uninstall scripts are now much more readable
  #361 Install guide now provides snippet on how to download latest release on Windows

### Installation
  #396 Added override user/password/tablespace for install_headless
  #384 Installation is now smooth even if profiler tables already exist

### Internal improvements
  #388 Improved reporting from RunTest
  #363 Fixed publishing of release documentation history

### Improvements and fixes
  #407 Fixed rare issue with `ORA-22813: operand value exceeds system limits`
  #403 Stack trace is now properly parsed on all machines
  #397 The `--%disabled` annotation on suite level is now reporting all tests as disabled
  #395 Coverage reporting is now properly filtering test packages on that use suitepath
  #390 Line of code for failed expectation is now also shown for unit tests owned by other users
  #380 Line no of failed test is now properly reported when using `ut.fail`
  #375 Annotation parameter list can now have spaces before/after brackets
  #373 Warnings in documentation reporter are now properly numbered
  #372 Documentation reporter is now providing a timing information for each test
  #370 by xUnit reporter now displays name of the package/procedure if suite/test has no description
  #369 Fixed errors with multi-byte characters in conversion from/to clob
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants