W Worker Member³ May 3, 2007 #1 This test script: Code: begin :result := rpad('x', 4001, 'x'); end; results in this error: Code: ORA-06502: PL/SQL: numeric or value error: character string buffer too small Is there any way to increase the size of ":result" from 4000 to 32767 characters?
This test script: Code: begin :result := rpad('x', 4001, 'x'); end; results in this error: Code: ORA-06502: PL/SQL: numeric or value error: character string buffer too small Is there any way to increase the size of ":result" from 4000 to 32767 characters?
C CTzen Member³ May 3, 2007 #1 Interesting, if I change your code a bit, debugger shows that l_result has "Long value", but doesn't show actual value. Code: declare l_result varchar2(32767); begin l_result := rpad('x', 4001, 'x'); end;
Interesting, if I change your code a bit, debugger shows that l_result has "Long value", but doesn't show actual value. Code: declare l_result varchar2(32767); begin l_result := rpad('x', 4001, 'x'); end;
Marco Kalter Administrator Staff member May 4, 2007 #1 If you declare the bind variable as "PL/SQL String" instead of "String", it can be upto 32KB.
W Worker Member³ May 4, 2007 #1 When right-clicking a function that returns a VARCHAR2 and choosing "Test", the test window is set up with bind variables of type "String" by default. Would maybe "PL/SQL String" be a better default type?
When right-clicking a function that returns a VARCHAR2 and choosing "Test", the test window is set up with bind variables of type "String" by default. Would maybe "PL/SQL String" be a better default type?
Stew Stryker Member³ May 9, 2007 #1 I'd agree with Worker there - PL/SQL String instead of SQL String for the default. I think it's pretty unlikely anyone would try to INSERT a test bind variable into a database table (which would need the shorter SQL String).
I'd agree with Worker there - PL/SQL String instead of SQL String for the default. I think it's pretty unlikely anyone would try to INSERT a test bind variable into a database table (which would need the shorter SQL String).
Roeland Member³ Mar 5, 2010 #1 Would maybe "PL/SQL String" be a better default type? Click to expand... Any update on this? If this couldn't be set as the default (I would like to hear the reasons), then maybe this could be made a setting. I would prefer this as a default. This goes also for the Oracle Wizard. Default type is "otString". Why does it work here and not in a Test window? Am I missing something? Thanks, Roeland
Would maybe "PL/SQL String" be a better default type? Click to expand... Any update on this? If this couldn't be set as the default (I would like to hear the reasons), then maybe this could be made a setting. I would prefer this as a default. This goes also for the Oracle Wizard. Default type is "otString". Why does it work here and not in a Test window? Am I missing something? Thanks, Roeland
Marco Kalter Administrator Staff member Mar 8, 2010 #1 I have added this to the list of enhancement requests.
Roeland Member³ Jan 21, 2015 #1 Would maybe "PL/SQL String" be a better default type? Click to expand... Still not implemented in v11 beta 3. This is a question from the year 2007! That is almost 8 years! How hard could it be? A very small change for you or a lot of annoying changes for all of your users... PS: Please update the Oracle Wizard also.
Would maybe "PL/SQL String" be a better default type? Click to expand... Still not implemented in v11 beta 3. This is a question from the year 2007! That is almost 8 years! How hard could it be? A very small change for you or a lot of annoying changes for all of your users... PS: Please update the Oracle Wizard also.