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 — special characters in connection name · Issue #118 · utPLSQL/utPLSQL-SQLDeveloper

special characters in connection name #118

New issue
Copy link
New issue
Copy link
Closed
#129
#119
Closed
special characters in connection name#118
#129
#119
Copy link
Assignees
PhilippSalvisberg
Labels
bug
Milestone
v1.3.0

Description

@wolframhaussig
wolframhaussig
opened on Dec 4, 2020
Issue body actions

It is just a minor beauty bug, but it would still be nice to see this fixed:
We have connections in the SQL-Developer named username@database, e.g. sys@local. When I use the button "run utplsql test" in sqldeveloper the utplsql shows the name wrongly in the history list:
image
Instead of SQL_TOOLS@lokal the UI shows SQL_TOOLS%40lokal

Activity

  1. PhilippSalvisberg commented on Dec 4, 2020

    @PhilippSalvisberg
    PhilippSalvisberg
    on Dec 4, 2020
    Member
    More actions

    Yes, I consider this a bug. Thanks for reporting.

  2. PhilippSalvisberg
    added
    bug
    on Dec 4, 2020
  3. PhilippSalvisberg
    self-assigned this
    on Dec 4, 2020
  4. PhilippSalvisberg
    closed this as completedin #119on Dec 26, 2020
  5. PhilippSalvisberg
    added this to the v1.3.0 milestone on Dec 26, 2020
  6. wolframhaussig commented on Jan 4, 2021

    @wolframhaussig
    wolframhaussig
    on Jan 4, 2021
    Author
    More actions

    @PhilippSalvisberg I have just tested your fix and it works: instead of %40 the @ sign will be displayed correctly. But I have found that the space character is displayed as a + sign (sorry for not finding that earlier)

  7. PhilippSalvisberg
    reopened this on Jan 4, 2021
  8. PhilippSalvisberg commented on Jan 4, 2021

    @PhilippSalvisberg
    PhilippSalvisberg
    on Jan 4, 2021
    Member
    More actions

    Thanks @wolframhaussig for checking. I wonder since when spaces are allowed in the connection name.

    image

    But I see that it works. Looks like they are treated in a special way. I'll fix that.

  9. wolframhaussig commented on Jan 4, 2021

    @wolframhaussig
    wolframhaussig
    on Jan 4, 2021
    Author
    More actions

    I am using version 20.2.0.175(Build 175.1842) but it worked before. I think it worked in version 18.x already but I am not sure when it started exactly.

  10. PhilippSalvisberg
    added a commit that references this issue on Jan 4, 2021

    fixes #118 (again) spaces are encoded as plus signs in connection names

    This issue will close once commit 78f0ae8 is merged into the 'main' branch.
    78f0ae8
  11. PhilippSalvisberg
    closed this as completedin #129on Jan 4, 2021
  12. PhilippSalvisberg
    added a commit that references this issue on Jan 4, 2021

    Merge pull request #129 from utPLSQL/bugfix/issue-124-double-click-on…

    6df7d05
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

    • v1.3.0

    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.