Thanks !
$dbh->do("begin dbms_output.enable(NULL); end;"); works well !
Sven Miller a écrit :
> The 20,000 character default is hardcoded in the DBD::Oracle
> implementation of dbms_output_enable. I don't see a way around it
> with the current implementation.
>
> But as a workaround, you could
The 20,000 character default is hardcoded in the DBD::Oracle
implementation of dbms_output_enable. I don't see a way around it
with the current implementation.
But as a workaround, you could probably replace your use of
dbms_output_enable with:
$dbh->do("begin dbms_output.enable(NULL); end;");
O
If a use
$dbh->func(undef,'dbms_output_enable');
It the same as :
$dbh->func('dbms_output_enable');
With DBI->trace(2), I see that it use the default buffer (20,000
bytes.).
Douglas Wilson a écrit :
> On Tue, Aug 5, 2008 at 11:38 PM, olwin <[EMAIL PROTECTED]> wrote:
> > Upper limit, in bytes,
On Tue, Aug 5, 2008 at 11:38 PM, olwin <[EMAIL PROTECTED]> wrote:
> Upper limit, in bytes, the amount of buffered information. Setting
> buffer_size to NULL specifies that there should be no limit.
>>
> Is there a way to specified a null size ?
>
> P.S : I use:
> DBD::Oracle : 1.15
> DBI : 1.42
>
Good morning,
I encounter a problem with DBMS_OUTPUT_enable.
In 10gR2, you can have an unlimited buffer size
Oracle doc :
buffer_size :
Upper limit, in bytes, the amount of buffered information. Setting
buffer_size to NULL specifies that there should be no limit.
But if I use :
DBI->
