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

NO_OP installer has references to logger_logs table #78

martindsouza opened this Issue Feb 19, 2015 · 1 comment


None yet
1 participant

martindsouza commented Feb 19, 2015

From @sChintamani on September 23, 2014 21:26

The no_op installer has anchored references to logger_logs table. This I found the hard way, once the script went to deployment into near PROD env.

We installed the regular version in DEV & QA environments and no_op version was required on the PROD env. When we ran the no_op version without un-installing the previous logger, the builds went fine and we didn't realize this anchoring until we hit PROD. I just now came back from this deployment (it's 3:00 AM in the morning :( !).. Please see the attached screen-shot for details.

Would be nice to have an updated script checked in into git-hub. I 'll be more than happy to contribute the updated version, we came up with.


Copied from original issue: tmuth#77

@martindsouza martindsouza self-assigned this Mar 16, 2015

@martindsouza martindsouza added this to the Release 3.1.0 milestone Mar 16, 2015

@martindsouza martindsouza added the bug label Mar 16, 2015

@martindsouza martindsouza removed their assignment May 1, 2015

martindsouza added a commit that referenced this issue May 29, 2015

@martindsouza martindsouza self-assigned this May 29, 2015


This comment has been minimized.


martindsouza commented May 29, 2015

There were several approaches we could have taken on this issue. The main two were as follows:

  • Create record types for all the object types and put in logger.pks. Developers would then need to reference these record types instead of the object types (ex: logger_logs.scope%type).
  • Create all the objects in the NO_OP script.

Decided to go with the second option. The NO_OP script will now install all the objects so if any of your code references it, queries from the views, etc it will still compile (though no data is stored).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment