RE: YES! YES! YES! ;-)

Martin Gainty <[email protected]>
Newsgroups gmane.comp.db.oracle.toad.free
Message-ID <[email protected]>
Norm

apparently direct writes to any LOB are verboten.. one should always invoke DBMS_LOB.WRITE(clob,length(varchar_input),1,varchar_input)

http://geekswithblogs.net/robertphyatt/archive/2010/03/24/write-read-and-update-oracle-clobs-with-plsql.aspx

since youve mastered SSH i take it you are now a Eunuchs guy?

Have Fun,
Martin Gainty 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.


To: [email protected]
From: [email protected]
Date: Wed, 26 Sep 2012 15:59:58 +0100
Subject: [toad] YES! YES! YES! ;-)
















 



  


    
      
      
      I've got Toad back again, I have found a way around our work firewalls 

that allows me to ssh tunnel from my laptop to the databases. I've been 

without Toad abilities for a year now, and I've hated having to use 

SQL*Plus for all that time. No more!



And now a question.



I am looking at a CLOB in an 11203 database with Toad 11.0.0.116 (I'll 

upgrade soon, I promise!) and I see in the hex tab of the pop-up editor, 

cr/lf end of lines. However, when I select a dump of a substring of the 

same CLOB actually on the database, in <spit> SQL*Plus, I only see the 

lf characters.



In my options I have the following set:



Oracle/General - Unix Style checked for "Newline format for character data"



Files/General - Save files in Unix format.



In Toad, when I dump the CLOB in MOE using a DBMS_LOB.SUBSTR() call, I 

see the last half dozen characters as:



61,74,61,3e,0a,00 Which = 'ata>' lf ? (where ? = a binary zero that 

shouldn't be there but is!)



On the server, I get exactly the same. Note Unix style line ends.



In the popup editor, hex tab, I get the following at the end:



61 74 61 3E OD OA OO Which = 'ata>' cr lf ?



Hmm, just found something. I edited the text to remove the unwanted and 

illegal (XML) binary zero at the end. When I saved it back to the table, 

it shows me "Unix style newlines (LF)" on the pop-up editor status line 

and on the hex tab, all the line ends are now still in Microsoft style, 

except the final one, which is in Unix style. Ulp!



Confused? Me? You bet!



-- 

Cheers,

Norm. [TeamT]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.