Dave, I really can't tell, without configuring what you have and you seem to be unable to describe your versions, etc, nor can you update to the latest DBD::ODBC...so....what I will conclude is:
It *may* be a bug in DBD::ODBC. It *may* be a bug in FreeTDS It *may* be a bug in unixODBC (sorry Nick!) It *may* be anything, but: a) isql uses different ODBC calls than DBD::ODBC does to retrieve data. b) I don't know which version of FreeTDS you are using, but *I* had problems with 0.53 and DBD::ODBC. The ODBC layer in FreeTDS didn't work well enough for my tests to pass. There is a newer version (0.60) fully released and that *may* be better, but I haven't had time to look at it. If I had to *guess* at this point: FreeTDS, the core protocol layer is probably fine. It's probably in DBD::ODBC and/or FreeTDS's ODBC layer. It's probably *not* unixODBC, but again, since you can't tell which versions and you are "a bit hazy" on what you did, makes it more difficult to pinpoint the problem. Jeff > -----Original Message----- > From: Dave Thorn [mailto:davet@;fysh.org] > Sent: Wednesday, October 23, 2002 6:25 AM > To: Jeff Urlwin > Cc: [EMAIL PROTECTED] > Subject: Re: :ODBC bug? > > > On Tue, Oct 22, 2002 at 12:47:31PM -0400, Jeff Urlwin wrote: > > > > I'd check on your versions of FreeTDS and unixODBC... > > So FreeTDS is broken, not DBD::ODBC, despite isql not showing the same > behaviour? If so i'll go and see if i can report a bug in that. > > -- > dave thorn | [EMAIL PROTECTED] >
