comment on

Thanks for the tip.

I have tried it now.

$sth = $dbh->prepare($sql);
$sth->execute();
my $lob;
my $chrs_or_bytes_read = $sth->odbc_lob_read(0, \$lob, 65535, { TreatA
+sLOB=>1 });
[download]

Results in .. Column 0 was not bound with TreatAsLOB

I guess this particular DBI method can only be used on columns that are bound to a prepare statement. If that's true, it can not be used in this instance. There is nothing to bind.

$sth = $dbh->prepare($sql);
$sth->bind_col(1, \$lob);
$sth->execute();
[download]

fails with

cannot bind to non-existent field 1
[download]

I am sending a DDL statement (show table) into the database, and expecting to get a DDL script of the particular table as output. Everything works fine up until to a certain size of the DDL script, then I am getting the "truncation" error mentioned in the original post.

Regards, Jan

In reply to Re^2: Strange DBI/DBD::ODBC behaviour (right truncation of data on ODBC call) by jahero
in thread Strange DBI/DBD::ODBC behaviour (right truncation of data on ODBC call) by jahero

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks