http://qs321.pair.com?node_id=664815


in reply to Re^3: Text retrieved from database column being truncated
in thread Text retrieved from database column being truncated

The new server now has the same version of FreeTDS and the config are supposed to be the same as well. I tried the DBI tracing option on both servers which revealed that there is a maxlen set to 4000 on the one but only 255 on the new server which results in column contents being truncated. This is an excerpt of the DBI tracing (level 5): 
-> prepare for DBD::Sybase::db (DBI::db=HASH(0x8d42418)~0x8d44360 'sel
+ect details from LogEntry
                    where logEntryId = 24516') thr#8b29008
    New DBI::st (for DBD::Sybase::st, parent=DBI::db=HASH(0x8d44360), 
+id=)
    dbih_setup_handle(DBI::st=HASH(0x8d444c8)=>DBI::st=HASH(0x8d4433c)
+, DBD::Sybase::st, 8d444d4, Null!)
    dbih_make_com(DBI::db=HASH(0x8d44360), 8d44c78, DBD::Sybase::st, 4
+20, 0) thr#8b29008
    dbih_setup_attrib(DBI::st=HASH(0x8d4433c), Err, DBI::db=HASH(0x8d4
+4360)) SCALAR(0x8cbfd34) (already defined)
    dbih_setup_attrib(DBI::st=HASH(0x8d4433c), State, DBI::db=HASH(0x8
+d44360)) SCALAR(0x8cbfd94) (already defined)
    dbih_setup_attrib(DBI::st=HASH(0x8d4433c), Errstr, DBI::db=HASH(0x
+8d44360)) SCALAR(0x8cbfd64) (already defined)
    dbih_setup_attrib(DBI::st=HASH(0x8d4433c), TraceLevel, DBI::db=HAS
+H(0x8d44360)) 0 (already defined)
    dbih_setup_attrib(DBI::st=HASH(0x8d4433c), FetchHashKeyName, DBI::
+db=HASH(0x8d44360)) 'NAME' (already defined)
    dbih_setup_attrib(DBI::st=HASH(0x8d4433c), HandleSetErr, DBI::db=H
+ASH(0x8d44360)) undef (not defined)
    dbih_setup_attrib(DBI::st=HASH(0x8d4433c), HandleError, DBI::db=HA
+SH(0x8d44360)) undef (not defined)
    syb_st_prepare() -> inUse = 0
    syb_st_prepare() -> set inUse
    <- prepare= DBI::st=HASH(0x8d444c8) at testbigchar.pl line 32 via 
+testbigchar.pl line 18
    -> execute for DBD::Sybase::st (DBI::st=HASH(0x8d444c8)~0x8d4433c)
+ thr#8b29008
    syb_alloc_cmd() -> CS_COMMAND 8d58a70 for CS_CONNECTION 8c81840
    cmd_execute() -> ct_command() OK
    cmd_execute() -> ct_send() OK
    cmd_execute() -> set inUse flag
    st_next_result() -> ct_results(4040) == 1
    ct_res_info() returns 1 columns
    ct_describe(0): type = 1, maxlen = 255
    describe() -> col 0, type 1, realtype 1
describe() retcode = 1
    st_next_result() -> lasterr = 0, lastsev = 0
    <- execute= -1 at testbigchar.pl line 33 via testbigchar.pl line 1
+8
    -> fetchrow_array for DBD::Sybase::st (DBI::st=HASH(0x8d444c8)~0x8
+d4433c) thr#8b29008
    dbih_setup_fbav for 1 fields => 0x8d45ed0
    fix_fbav() -> num_fields = 1, numCols = 1
    syb_st_fetch() -> ct_fetch() = 1 (1 rows)
    syb_st_fetch() -> 0/255/1
    <- fetchrow_array=...

[download]
The question is: How do I set/override the maxlen? I have tried a couple of things, which haven't worked.

Replies are listed 'Best First'.
Re^5: Text retrieved from database column being truncated
by mpeppler (Vicar) on Jan 29, 2008 at 07:35 UTC
    The maxlen value is retrieved through the API - it's what Client Library (or in this case, FreeTDS) tells us that it is for this particular datatype/column.

    You may want to ask on the freetds mailing list about this - I'm not a FreeTDS specialist by any means. However, the limitation is related to the TDS protocol version - if the client connects with TDS 4.2 then you won't be able to get wide varchar() columns, for example.

    Michael

[reply]
[d/l]
Re^5: Text retrieved from database column being truncated
by mpeppler (Vicar) on Jan 29, 2008 at 07:37 UTC
    I just noticed that you say
    the config files are supposed to be the same
    Please make sure that this is really the case - otherwise I would bet that the problem is with the TDS protocol version that is used.

    Michael

[reply]
      Hi Michael,

      I thought you might appreciate an update to the perl issue that I was encountering. The problem was actually caused by only root having permissions to the freetds.conf file.

      Thanks

[reply]

In Section Seekers of Perl Wisdom