DBD is as DBD does

MiniMe · Post by **MiniMe** » Tue Dec 17, 2002 5:11 pm

I have a small app that executes this query:

select refund.salesorder, refund_amt, CCnumber, CCexp from refund, processed where refund.salesorder != '' and refund.salesorder = processed.salesorder

In TSQL this query works great. In perl I only get the first 2 colunms. the 2nd two are always blank. Ideas?

Post by **John** » Tue Dec 17, 2002 5:55 pm

Not immediately. What types are the columns?

MiniMe · Post by **MiniMe** » Tue Dec 17, 2002 7:03 pm

they are 3 varchar and 1 float.. dbitrace shows this, which is incorrect:

-> execute for DBD::TEXIS::st (DBI::st=HASH(0x1403d09a0)~0x140417dd8)
dbd_st_execute (for sql f1073945632 after)...
dbd_describe sql 1073945632: num_fields=4
col 1: CHAR len= 0 disp= 1, prec=2000 scale=0
col 2: CHAR len= 0 disp= 1, prec=2000 scale=0
col 3: CHAR len= 20 disp= 21, prec=2000 scale=0
col 4: FLOAT len= 20 disp= 21, prec= 20 scale=0
col 1: 'processed.CCnumber' sqltype=CHAR, ctype=SQL_C_CHAR, maxlen=1
col 2: 'processed.CCexp' sqltype=CHAR, ctype=SQL_C_CHAR, maxlen=1
col 3: 'refund.salesorder' sqltype=CHAR, ctype=SQL_C_CHAR, maxlen=21
col 4: 'refund.refund_amt' sqltype=FLOAT, ctype=SQL_C_CHAR, maxlen=21
<- execute= '0E0' at processrefund.pl line 42.

Does the DBD get the info from SYSCOLUMNS as to field lengths...??