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 — Cannot install tests when using default user names as provided in template.env.sh · Issue #1200 · utPLSQL/utPLSQL

Cannot install tests when using default user names as provided in template.env.sh #1200

New issue
Copy link
New issue
Copy link
Closed
#1201
Closed
Cannot install tests when using default user names as provided in template.env.sh#1200
#1201
Copy link
Assignees
jgebal
Labels
bug

Description

@PhilippSalvisberg
PhilippSalvisberg
opened on Mar 13, 2022
Issue body actions

Describe the bug

In template.env.sh the user name UT3$USER# is configured for ${UT3_USER}. In install_ut3_tester_helper.sql the user is hard coded. ut3_user is used.

When I use an env.sh based on template.env.sh and do not change the default users then running test/install_and_run_tests.sh produces an error while running this statement create or replace synonym ut3_user.coverage_helper for ut3_tester_helper.coverage_helper; because the user ut3_user does not exist.

Expected behavior

Installation of tests work when using the default usernames in template.env.sh.

Workaround

Configure export UT3_USER=UT3_USER in env.sh.

Off topic remark

I do not see a value in making the test users configurable. Quite the contrary. It makes the the test setup more complicated and also more fragile. Making the utPLSQL schema owner for production use configurable makes sense. But the testing users? - I don't think so.

Activity

  1. PhilippSalvisberg
    added
    bug
    on Mar 13, 2022
  2. jgebal commented on Mar 13, 2022

    @jgebal
    jgebal
    on Mar 13, 2022
    Member
    More actions

    Hi @PhilippSalvisberg
    I agree with you on that one.
    There is no need to have those configurable and having them hard-coded would make things much clearer.
    It would be definitely good to clean this up.

    Reacted by Philipp Salvisberg
  3. jgebal
    self-assigned this
    on Mar 13, 2022
  4. jgebal
    closed this as completedin #1201on Mar 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @jgebal
    jgebal

Labels

bug

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.