Mittwoch, November 08, 2006

EMPTY_CLOB() really required?

Help my PL/SQL works - [ ja darf es denn das?]

Contrary to all advises I don't try to initialise CLOB Fields with empty_clob().
And not wanting to use SQL*Loader (need to many distinct files). I use code like the following:

drop table tmp_test_bk1;

set escape off
set escape '\'

create table tmp_test_bk1 (id number(10), wert clob);

insert into tmp_test_bk1 (id) values (1);

declare
v_wert clob;
begin
v_wert := '

...
and many, many more lines, giving more than 64000 Bytes
inspite of the limit of 4000 Bytes
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:1019631214472
....
'
;
update tmp_test_bk1 set wert = v_wert where id = 1;
end;
/

select length(wert) from tmp_test_bk1;

using a script which some real data , using
Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
I get no Problems but the following result:

LENGTH(WERT)
------------
64206

Finding no current tools able to display long multiline contents in databases without some clipping, caueses me to build something in Iron Python for Oracle and for SQL-Server

In a few days I'll put the IronPython Code in some repository, so that you don't have to fiddle around with the old copy&waste [I really mean waste] technologie, so be patient.

Just have to prepare the usual disclamers:
Rauchen schadet Ihrer Gesundheit
Wegen der Nebenwirkungen fragen sie ihrern Arzt oder Apotheker
[translation to englisch wanted]
meanig that you can freely use the code examples but absolutely at your own risk.
And I have to organise the folder structure. Restructioning of repositories is no fun, so I'll better do it right in the beginning.



2 Kommentare:

Unknown hat gesagt…

Your translated disclaimer:
"Smoking damages your health
On account of the side effects, ask your doctor or pharmacist"

I'm sorry, I don't have enough CLOB experience to comment on your real questions...

Bernd Kriszio hat gesagt…

Thanks for the translation Cathrine.
Perhaps it is meanly a problem of search engines showing often old stuff. Anycase it seems to work at my databases at least for maintenance PL/SQL Scripts. Using application access via DAO, ADO or ADO.Net I' still unsure.