GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Question - limiting the types to ignore triggers · Issue #215 · utPLSQL/utPLSQL-cli

Question - limiting the types to ignore triggers #215

New issue
Copy link
New issue
Copy link
Open
Open
Question - limiting the types to ignore triggers#215
Copy link
Labels
question

Description

@clarkec21
clarkec21
opened on Dec 23, 2022
Issue body actions

Hi
I am calling utplsql-cli via GitHub Actions on a runner server on OCI as ADMIN user. I pass in multiple schemas to be processed and am writing the documentation to a file and coverage html to a file. My question is: I do not want to report on coverage for triggers and I am not using Projects and files I am only using the database. Can yo advise how I do this.

Activity

  1. jgebal commented on Jan 16, 2023

    @jgebal
    jgebal
    on Jan 16, 2023
    Member
    More actions

    At the moment there is no way to include/exclude objects in coverage by object type in utPLSQL core framework.
    Also, the option for inclusion/exclusion of objects by regular expression is not implemented in utPLSQL-cli.

    So your only option currently would be to provide a long list of object names to exclude.

    It seems like a potential gap in utPLSQL capabilities.

    Do you have a naming convention for triggers that would make it possible to exclude objects by part of name (prefix/suffix etc?)
    Would filtering by list of object_names be an option?

    Why does it hurt to have Triggers in the report? Are they not part of the project source-code?

  2. jgebal
    added
    question
    on Jan 16, 2023
  3. clarkec21 commented on Feb 3, 2023

    @clarkec21
    clarkec21
    on Feb 3, 2023
    Author
    More actions

    Hi @jgebal thnks for your reply

    I should have explained our triggers either contain calls to packages (already utplsql tested) or standard code auto generated by us to write to history/journal tables - the testing of these is a bit of an overhead.

    We do have a standard naming convention but wildcards are not utilised so I would have to maintain a large ever changing list - we can just include in the coverage report them but ignore their % for now. Any progress on Issue 212 should help us.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    question

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.