Request: Large Data Editor should shift to Text tab page when XML parsing fails

[Claus Pedersen]

I am editing some CLOB's in a table. Some of the CLOB content is XML, so the large data editor opens with the XML tab page active. But because the CLOB can not be parsed as correct XML, the window just shows an error message.

Is it possible that PLD could automatically shift to the Text tab page if XML parsing fails when editor is opened? Today I have to change to the Text tab page manually each time, and this is quite annoying.

Best regards
Claus Pedersen

 

[Marco Kalter]

I have added this to the list of enhancement requests. As a workaround, you can switch to the "External" tab page and associate the column to an external text editor like notepad or wordpad. If you enable the "Execute automatically next time" option, the column will always be displayed through this external program.

 

[Claus Pedersen]

OK, thanks

 

[Frank Kintrup]

Originally posted by Marco Kalter:
I have added this to the list of enhancement requests. As a workaround, you can switch to the "External" tab page and associate the column to an external text editor like notepad or wordpad. If you enable the "Execute automatically next time" option, the column will always be displayed through this external program.

Unfortunately, this does not always work.

I tried to associate the FirstObject XML editor with my xml-CLOBs, but it only shows the opening bracket "

 

[Marco Kalter]

Hmm, this may indeed be a character encoding error. We'll fix it.

 

[Marco Kalter]

I tried to associate the FirstObject XML editor with my xml-CLOBs, but it only shows the opening bracket "