I agree to Idea XMLTYPE Editing - Schema Browser (Data Tab)
Voting Disabled

27 votes

I disagree to Idea XMLTYPE Editing - Schema Browser (Data Tab)

Rank30

Idea#433

This idea is active.
Schema Browser »

XMLTYPE Editing - Schema Browser (Data Tab)

I would like to see the XMLTYPE functionality from 9.7 re-implemented in to Toad. This functionality includes the ability to edit XMLTYPE fields in Schema Browser (Data Tab). Very useful if you are an XML developer.

Submitted by Community Member 3 years ago

Comments (13)

  1. This is pretty much the only killer feature we use TOAD 9.7 for. We're unable to upgrade until this is put back in or adequately replaced. It's only a matter of time before SQL*Developer has this feature and at that point we might seriously consider switching if TOAD does not have the functionality.

    Using an external editor is not really a good substitute for quick editing, it's clunky and has problems... for example, files left open in the editor once you sync back, etc.

    3 years ago
    1 Agreed
    0 Disagreed
  2. AGREEEEEEE!!!!!!!!!!

    Please put this function back into TOAD.. want to use new features in current version but can not with out this being put back into the product. Do not want to have to run one version when doing xml work and another when not doing xml work....

    2 years ago
    0 Agreed
    0 Disagreed
  3. Moderator

    We hear you. This is something we'd like to support but the OCI in unicode mode doesn't play nice with XMLTYPE. As soon as an Oracle client comes along that works, we'll support it again. In the meantime, if you store your XML data in CLOBs you should be able to edit the data in Toad.

    2 years ago
    0 Agreed
    0 Disagreed
  4. "In the meantime, if you store your XML data in CLOBs"

    This is easier said than done will require development to agree, potential code change as they are configured to use what is configured currently. Not sure we will be able to make that change in our environment.

    2 years ago
    0 Agreed
    0 Disagreed
  5. Moderator

    I understand, and I'm not trying to tell you what you should or shouldn't do...just what will and won't work in Toad.

    2 years ago
    0 Agreed
    0 Disagreed
  6. This seems to be resolved in TOAD 11, although I couldn't find anything in the change logs.

    2 years ago
    0 Agreed
    0 Disagreed
  7. Moderator

    It's not resolved in Toad 11. You can view the data (as long as it isn't stored in binary XML), but not edit it.

    2 years ago
    0 Agreed
    0 Disagreed
  8. Our workaround is to use Oracle's SQL Developer for viewing tables with XMLType. We use TOAD 11 for any other tasks.

    I was the one who introduced TOAD in our company but if SQL Developer catches on the main features that we normally use in TOAD, I will be the one to lead the switch too.

    It's so annoying when TOAD crashes because you accidentally click the Data tab in Schema Browser while inspecting an XMLType table.

    I would suggest that access to the Data tab should be disabled for XMLType tables or disable any part of TOAD that will crash on XMLType objects.

    2 years ago
    0 Agreed
    0 Disagreed
  9. Moderator

    It would be easy to add an option to just not include XMLTYPE columns from the select statements. In fact, if you go into options -> Schema Browser -> Data Tab, and uncheck "Don't select BLOB/CLOB fields" then we will leave XMLTYPE columns out of the select statement that loads the data tab. Of course that option also applies to all BLOB and CLOB columns, but I could add another option that applies only to XMLTYPE.

    2 years ago
    0 Agreed
    0 Disagreed
    1. Adding "Don't select XMLType fields" option will work for us.

      Make it default to Checked when you implement it on the next update.

      Thanks!

      2 years ago
      0 Agreed
      0 Disagreed
  10. Moderator

    I've noticced that if the XMLTYPE is stored as Binary, Toad has a problem, but if it is stored as CLOB, Toad is OK, as long as the Oracle client is 10g or newer.

    I've found that I can work around the "Stored as Binary" problem when by querying those columns like this:

    select XMLColumnName.GetClobVal() as XMLColumnName

    from...

    then Toad doesn't have any problems.

    Can you confirm that prevents the error for you too? If so, I can just always use GetClobVal for binary XMLTYPE and the problem goes away.

    2 years ago
    0 Agreed
    0 Disagreed
  11. I found on the net that there is a flag to define if Unicode is supported.

    OraCall.OCIUnicode := True

    Isn't it possible to have this flag as an option in TOAD meaning that it's possible to update XMLTYPE if we don't need Unicode support?

    I also got a description from Oracle how to do the update with SQL Developer.

    I creates a table testxml

    id number

    xmlcol xmltype

    and I inserted

    some data

    - 1.png shows the table

    - 2.png

    then I double click on the xml field

    you see a small pen on the right side of the field

    - I clickon the pen and an editor window is opened: 3.png

    - in the editor window you click on the Edito link and you see a new tab in SQL Developer.

    4.png

    From here you can change the content

    save it pressing the diskette like icon

    - now it redirects you to the tab where the table is shown: press the recycle icon.

    See the updated data : 5.png

    This means that it's possible to do it.

    2 years ago
    0 Agreed
    0 Disagreed
    1. Moderator

      SQL Developer uses JDBC to connect to Oracle. Toad uses OCI. The bug is in the OCI. That's why SQL Developer can update XML but not Toad.

      You are correct about the OCIUnicode flag. But to have Toad sometimes support unicode and sometimes not, depending on options, could cause more problems than it solves.

      2 years ago
      0 Agreed
      0 Disagreed

Events

  1. The idea was posted
    3 years ago