Re: DBD::Oracle -- NULL LOB Locator is not "null"
- From: scoles@xxxxxxxxxxx (John Scoles)
- Date: Tue, 29 May 2007 14:28:47 -0400
I think there was a patch for that one submitted but not released a while
ago. I will test this against the the current version and see what I get.
""Sven Miller"" <ngdvakigyotuia@xxxxxxxxx> wrote in message
news:8646c5f30705241108p6f24bfc1r51f532619ef5f540@xxxxxxxxxxxxxxxxx
(DBD::Oracle version 1.17)
Given the following:
my $sLobLocator;
my $hSQL = $hDB->prepare(q{
BEGIN
:lob := NULL;
END;
}, { ora_auto_lob => 0 });
$hSQL->bind_param_inout( ':lob', \$sLobLocator, 0, { ora_type =>
ORA_BLOB } );
$hSQL->execute;
print "\$sLobLocator = $sLobLocator\n";
print "\$\$sLobLocator = $$sLobLocator\n";
The output is:
$sLobLocator = OCILobLocatorPtr=SCALAR(0x1632d10)
$$sLobLocator = 25412916
I expected for $sLobLocator to be undefined or empty, or at least for
$$sLobLocator to be 0. Is this a bug, or is this by design? If this
is by design, is there a proper way to determine whether a LOB Locator
contains NULL?
Thanks for any insight!
.
- References:
- DBD::Oracle -- NULL LOB Locator is not "null"
- From: Sven Miller
- DBD::Oracle -- NULL LOB Locator is not "null"
- Prev by Date: Problem with Long Varchar Ingres Linux
- Next by Date: Incompatibility with DBI v1.56 / DBD::Sybase v1.08 / DBIx::ContextualFetch v1.03
- Previous by thread: Re: DBD::Oracle -- NULL LOB Locator is not "null"
- Next by thread: Problem with Large Query Returns from MS-SQL
- Index(es):