Skip to Content.
Sympa Menu

freetds - RE: [freetds] DBD::Sybase 1.01 & FTDS 0.62-dev & temp tables

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] DBD::Sybase 1.01 & FTDS 0.62-dev & temp tables
  • Date: Mon, 1 Dec 2003 16:31:15 -0500

> From: Jerry Grooms [mailto:grooms AT uky.edu]
> Sent: December 1, 2003 2:42 PM
>
> Hello,

Hello,

> I had to upgrade from FTDS 0.61 to 0.62-dev due to the "queries that
> return 0 rows" bug; (kudos to the DBD::Sybase release notes)
>
> The above was corrected and things are mostly working except for
> previously working (unchanged) queries that utilize temporary
> tables. eg select blah,blah INTO #some_totals ...
>
> An example of what I'm seeing is:
>
> DBD::Sybase::st execute failed: Server message number=208
> severity=16 state=0 line=3 server=blah-blah text=Invalid object name
> '#proj_totals'. at ./topten_lastmonth.pl line 131.

One change from 0.53 is that FreeTDS no longer identifies itself as an ODBC
driver (unless the ODBC driver is used). That affects default column
nullability (and other things). I don't see how that could affect anything
here, but it's worth keeping in mind.

If we could see a TDSDUMP log, that would help. It's possible, as Frediano
says, that DBD::Sybase is opening a second connection. That would explain
the nonexistence of the temp table.

It's also possible FreeTDS is falsely reporting busy-ness, inducing
DBD::Sybase to create a new connection when it doesn't (as far as the
server's concerned) really need to. If that's the case, you've got our full
attention, because we'd want that fixed before the release.

--jkl
-----------------------------------------
The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the original
message. Please note that we do not accept account orders and/or instructions
by e-mail, and therefore will not be responsible for carrying out such orders
and/or instructions.






Archive powered by MHonArc 2.6.24.

Top of Page