Sven Köhler пишет:
I have the same problem with UTF8 as with 7.6.00.16. I try to fetch LONG
column in UTF-8 from Perl::DBD. The first LONG column in the first row
is fetched wrong. I have 412 symbols but SQLDBC returns only 216
symbols. For this column SQLDBC returns indicator == SQLDBC_NO_TOTAL.
And the symbol in 216th position is zero. For other rows indicator is
not equals to SQLDBC_NO_TOTAL. Only for the first row.
I have no problems fetching the same data in SQL STUDIO and JDBC driver.
Only in SQLDBC.
Have you already got an answer from the MaxDB Team?
No any answers.
Is it really that deterministic? I just have to do a
SELECT long_column FROM table
And then i get a trucated string?
Everything else is properly setup? (the parameters of the DBI connection
concerning longs)
We have already successfully used SQLDBC from Perl and PHP to _read_
LONGs from the database. Until now, nobody discovered something truncated.
I use DBPROCs for returning resultsets. I have truncated only the first
row only in one DBPROC. After modifications in LONG or in DBPROC data
the bug is not reproducable.
Can somebody explain me in sqldbctrace file how many symbols in the field?
LONG DESCRIPTOR (maxlen=824, internpos=433,
infoset=(with_lock|unicode), valmode=0 (vm_datapart), valind=0,
valpos=130401, vallen=432)
vallen=432/2=216 symbols? It is not true.
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
