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 — Restricted columns in cursor compare · Issue #997 · utPLSQL/utPLSQL

Restricted columns in cursor compare #997

New issue
Copy link
New issue
Copy link
Closed
#999
Closed
Restricted columns in cursor compare#997
#999
Copy link
Assignees
jgebal
Labels
bug
Milestone
v3.1.9

Description

@jgebal
jgebal
opened on Sep 22, 2019
Issue body actions

Describe the bug
Due to the nature of cursor comparison implementation, when comparing cursor containing one of column names:

  • ITEM_DATA
  • DATA_ID
  • ITEM_NO
  • DUP_NO
  • POSITION

The cursor comparison fails.

Provide version info
utPLSQL v3.1.8

To Reproduce
This can be observed on 3.1.8 with following block:

set serverout on
declare
  l_actual   sys_refcursor;
  l_expected sys_refcursor;
begin
  open l_actual   for select * from all_arguments where rownum = 1;
  open l_expected for select * from all_arguments where rownum = 1;
  ut.expect(l_actual).to_equal(l_expected);
end;
/

Expected behavior

utPLSQL should not prevent column names that are commonly used / possible to use.

One idea would be to use quoted and more unusual names for internal columns in cursor compare: "UT3$_Item#Data"

Reacted by Philipp Salvisberg

Activity

  1. jgebal
    added
    bug
    on Sep 22, 2019
  2. jgebal
    self-assigned this
    on Sep 22, 2019
  3. jgebal
    added 2 commits that reference this issue on Sep 22, 2019

    Changed names on internal columns in cursor & object compare.

    This issue will close once commit 108abae is merged into the 'develop' branch.
    108abae

    Changed names on internal columns in cursor & object compare.

    This issue will close once commit 169d0fe is merged into the 'develop' branch.
    169d0fe
  4. jgebal
    added this to the 3.1.9 milestone on Sep 22, 2019
  5. jgebal
    closed this as completedin #999on Sep 23, 2019
  6. apexbine commented on Mar 7, 2020

    @apexbine
    apexbine
    on Mar 7, 2020
    More actions

    Also bumped into the 'position bug'.
    To make this issue easier to find, I'll just mention ORA-00918: column ambiguously defined.

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

    • v3.1.9

    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.