Michael,

  Yes.  It's FreeTDS.  

  In researching this issue, I ran across this in the archives:

        http://aspn.activestate.com/ASPN/Mail/Message/perl-DBI/299919

   I'm on Redhat and using fetchrow_hashref, but the issue is the same as
this 2000 issue.

   I saw reference to the issue in the DBI list archives for a few weeks
back, but Google took me to a broken link, so I was able to see what went
on.  However, it appears that you responded to them in some way because your
email is viewable in the Google listing regards the issue.

   I'm running TDS .61 (the newest stable) and DBD::Sybase 0.95.  I'm aware
that Sybase TDS and Microsoft are heading off in differing directions.  I
just wanted to know if there was an easy fix I could introduce in the setup
on my packages' ->new() call or if I have to wrap everything up in eval
statements until I go through and right TSQL calls to check if the dumb
things exist or not.

Thanks,
Karyn

-----Original Message-----
From: Michael Peppler [mailto:[EMAIL PROTECTED]
Sent: Monday, March 31, 2003 2:02 PM
To: '[EMAIL PROTECTED]'
Subject: Re: New fetchrow behavior in DBD::Sybase??


On Mon, 2003-03-31 at 11:36, Karyn Ulriksen wrote:
> Hi All,
> 
>    I recently upgraded one of my machines to DBD::Sybase 0.95.  I am
seeing
> a new behavior that is causing me problems and wondered if anyone could
help
> me out.
> 
>    Also, I'm seeing that "$self->{DBH}->{LongReadLen} = 65536;"  is being
> complained about in the logfiles, so I've remarked them out and hoping
that
> my "$self->{DBH}->do("set textsize 65536");" is doing the job.  If anyone
> has insight on what's up with that, I'd be much obliged.

Are you using FreeTDS?

> This worked pretty well before.  But, now, it appears that if the result
of
> the query is a null set, it pukes with a:
> 
>    Can't get DBI::st=HASH(0x811cfa8)->{NAME}: unrecognised attribute at
<my
> package>

Hmmm - I don't think that this is a problem with DBD::Sybase. However I
believe that there was (or maybe still is) a bug with FreeTDS and empty
result sets where the columns don't get set up correctly.

Michael
-- 
Michael Peppler                              Data Migrations, Inc.
[EMAIL PROTECTED]                 http://www.mbay.net/~mpeppler
Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short or 
long term contract positions - http://www.mbay.net/~mpeppler/resume.html

Reply via email to