Re: Sybperl 2.18 and temporary tables

I have zero experience with Sybase or Sybperl, but some things I would check are:

are you actually creating the temp table? Maybe break the single exec into parts to ensure each piece works
permissions, has the upgrade changed the user that the DB connection is made as? Can the current user connection create tables?

I have been burned by these types of things before when I updated a module. Figured I would toss those out...

...the majority is always wrong, and always the last to know about it...
The Spice must flow...
..by my will, and by will alone.. I set my mind in motion

Comment on Re: Sybperl 2.18 and temporary tables

Replies are listed 'Best First'.
Re^2: Sybperl 2.18 and temporary tables by Redwing (Initiate) on Feb 01, 2011 at 12:07 UTC
Thanks wjw, Actually the problem code works under the previous version. And all other code (except any code which looks to return rows from a temporary table) works fine under the new version so the connection and permissions must be correct. It really seems as if the 2.18 version of Sybperl lacks the functionality the 1.x versions had. The Sybperl::DBlib module also seems to have the same problem. Haven't had a chance to check the Sybperl::CTlib module yet. Anyway, thanks for your response! Redwing.	[reply]

Replies are listed 'Best First'.

Re^2: Sybperl 2.18 and temporary tables
by Redwing (Initiate) on Feb 01, 2011 at 12:07 UTC

Thanks wjw,

Actually the problem code works under the previous version. And all other code (except any code which looks to return rows from a temporary table) works fine under the new version so the connection and permissions must be correct. It really seems as if the 2.18 version of Sybperl lacks the functionality the 1.x versions had. The Sybperl::DBlib module also seems to have the same problem. Haven't had a chance to check the Sybperl::CTlib module yet.

Anyway, thanks for your response! Redwing.

[reply]