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 — Connection of unshared worksheet created by utPLSQL extension stays open after closing worksheet · Issue #47 · utPLSQL/utPLSQL-SQLDeveloper

Connection of unshared worksheet created by utPLSQL extension stays open after closing worksheet #47

New issue
Copy link
New issue
Copy link
Closed
Closed
Connection of unshared worksheet created by utPLSQL extension stays open after closing worksheet#47
Copy link
Assignees
PhilippSalvisberg
Labels
bug
Milestone
v0.6.4

Description

@PhilippSalvisberg
PhilippSalvisberg
opened on Oct 28, 2018
Issue body actions

If in the preferences "Open an unshared worksheet?" is checked, then a unshared worksheet is opened for every "Run utPLSQL test" call. So far so good.

When this unshared worksheet is closed, the connection stays open in the background. Even "Disconnect" is issued from Connections navigator tree on various levels.

Activity

  1. PhilippSalvisberg
    added
    bug
    on Oct 28, 2018
  2. PhilippSalvisberg
    added this to the v0.6.4 milestone on Oct 28, 2018
  3. PhilippSalvisberg
    self-assigned this
    on Oct 28, 2018
  4. PhilippSalvisberg commented on Oct 28, 2018

    @PhilippSalvisberg
    PhilippSalvisberg
    on Oct 28, 2018
    MemberAuthor
    More actions

    Using a temporary connection instead of a private connection seems to solve the problem. However, temporary Connections are a newer concept. They have been introduced in SQL Developer 17.4.0.

    Fixing this issue by breaking compatibility to SQLDev versions < 17.4.0 seems wrong.

    Further investigation is required.

  5. PhilippSalvisberg commented on Oct 28, 2018

    @PhilippSalvisberg
    PhilippSalvisberg
    on Oct 28, 2018
    MemberAuthor
    More actions

    Looks like the behavior of private connections changed in SQLDev 17.4.0. Solution is to use private connections in older SQLDev versions and temporary connenctions in newer SQLDev versions. Newer = 17.4.0 and higher.

  6. PhilippSalvisberg
    closed this as completedin 87eeda0on Oct 28, 2018
  7. PhilippSalvisberg
    added a commit that references this issue on Oct 28, 2018

    Merge pull request #48 from PhilippSalvisberg/develop

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

Metadata

Metadata

Assignees

  • @PhilippSalvisberg
    PhilippSalvisberg

Labels

bug

Type

No type

Projects

No projects

    Milestone

    • v0.6.4

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402520 — 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.