Xref: alice comp.databases.oracle.misc:42102 comp.databases.oracle.tools:32579
Path: alice!news-feed.fnsi.net!newspump.monmouth.com!newspeer.monmouth.com!dispose.news.demon.net!demon!nntp.news.xara.net!xara.net!gxn.net!news-lond.gip.net!news-raspail.gip.net!news.gsl.net!gip.net!oleane!wanadoo.fr!not-for-mail
From: Yann Chevriaux <chevriaux@theleme.com>
Newsgroups: comp.databases.oracle.misc,comp.databases.oracle.tools
Subject: Re: LONG Field / 7.3.4 / PL-SQL
Date: Tue, 28 Sep 1999 14:47:12 +0200
Organization: =?iso-8859-1?Q?Th=E9l=E8me?=
Message-ID: <37F0B8D0.275C36E2@theleme.com>
References: <37F0B01D.B5294EBB@ctp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: wanadoo.fr 938522780 15788 164.138.7.1 (28 Sep 1999 12:46:20 GMT)
X-Complaints-To: abuse@wanadoo.fr
NNTP-Posting-Date: 28 Sep 1999 12:46:20 GMT
Cc: Bruno Plankensteiner <bplank@ctp.com>
X-Mailer: Mozilla 4.51 [fr] (Win95; I)
X-Accept-Language: fr
Lines: 43

Bruno,

I'm sorry but ...

  YES ! PL/SQL long type is 32 K limited. I already asked something like that:.

Search for "Transferring LONG RAW from TAB1 to TAB2" in this forum (16/09/1999 17:42).

 I get some advices to fetch long columns.

You can also try: http://govt.us.oracle.com/~tkyte/

Good luck.

Bruno Plankensteiner a écrit :

> Hi
> I have a stored procedure which does the following:
>
> add a string to a long field in a table_case
>
> If the long has more than something like 36K bytes I get the error 6502
>
> -----------------------------------------------------------------------------
>
> APPEND_CASE_HISTORY(obj IN NUMBER, note IN VARCHAR, ret OUT VARCHAR)
> AS
>  prev_history long;
> BEGIN
>  select case_history into prev_history from table_case where objid=obj;
>  prev_history:=prev_history || note;
>  update table_case set case_history=prev_history where objid=obj;
>  commit;
> END APPEND_CASE_HISTORY
> --------------------------------------------------------------------------------------
>
> There is a limit of 36K if you select a long type into a long. Do you
> know a workaround?
>
> Thank you
>
> Bruno