Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus?
- From: Bill Myers <bwmyers@xxxxxxxxx>
- To: Steve Baldwin <stbaldwin@xxxxxxxxxxxxxxxx>
- Date: Thu, 2 Sep 2010 01:48:53 +0000
Thanks Steve, I overlooked the obvious with that one (the math looked off
which took precedence I suppose).
On Thu, Sep 2, 2010 at 12:17 AM, Steve Baldwin
<stbaldwin@xxxxxxxxxxxxxxxx>wrote:
> The problem in this case is that the data type of 'id || id' is VARCHAR2
> and with Oracle, the maximum size of a VARCHAR2 column is 4000 chars.
>
> Steve
>
>
> On Thu, Sep 2, 2010 at 10:06 AM, Bill Myers <bwmyers@xxxxxxxxx> wrote:
>
>> "id||id" is 4000 chars concatenated with another 4000 chars, so shouldn't
>> linesize=8000 in that case?
>>
>>
>> On Wed, Sep 1, 2010 at 4:40 PM, Michael Dinh <mdinh@xxxxxxxxx> wrote:
>>
>>> Here is a simple test case. May be I am doing something wrong, but was
>>> not able to figure it out.
>>>
>>>
>>>
>>> create table t1(id varchar2(4000));
>>>
>>> insert into t1 values (lpad('a', 4000, 'b' ));
>>>
>>>
>>>
>>> set linesize 4000
>>>
>>>
>>>
>>> select id||id from t1;
>>>
>>> ERROR at line 1:
>>>
>>> ORA-01489: result of string concatenation is too long
>>>
>>> ---------------------------------------------------------------------------------------
> This email is intended solely for the use of the addressee and may
> contain information that is confidential, proprietary, or both.
> If you receive this email in error please immediately notify the
> sender and delete the email.
> ---------------------------------------------------------------------------------------
>
>
>
- References:
- Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus?
- From: Bill Myers
- RE: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus?
- From: Michael Dinh
- Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus?
- From: Bill Myers
- RE: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus?
- From: Michael Dinh
- Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus?
- From: Bill Myers
- Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus?
- From: Steve Baldwin
- Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus?
Other related posts:
- » Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Bill Myers
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Jared Still
- » RE: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Michael Dinh
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - John Piwowar
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Bill Myers
- » RE: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Michael Dinh
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Steve Baldwin
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Bill Myers
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Rumpi Gravenstein
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Steve Baldwin
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - De DBA
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - De DBA
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Bill Myers
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Subodh Deshpande
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - William Robertson
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Howard Latham
- » RE: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Bellows, Bambi (Comsys)
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Greg Rahn
- » RE: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Goulet, Richard
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Jared Still
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Jeremy Schneider
- » RE: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Powell, Mark
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Andreas Piesk
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Bill Ferguson
- » RE: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Goulet, Richard
- » RE: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Powell, Mark
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Bill Myers
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Peter Hitchman
- » Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus? - Subodh Deshpande