Edit t/main.t and uncomment the "print" below:

else {
    print "ok 7\n";
    ($DBI::err == 208)
    and print "ok 8\n"
        or print "not ok 8\n";
#    print STDERR ($DBI::err, ":\n", $sth->errstr);
}
[download]

Re-run the script with

perl -Mblib t/main.t
[download]

Michael

Here's the output:

nod019 (v12_5) > perl -Mblib t/main.t
1..19
ok 1
Switch: DBI 1.43 by Tim Bunce, 1.43
Available Drivers: DBM, ExampleP, File, Proxy, Sponge, Sybase
Connect to server version: 12.5.0.3
ok 2
ok 3
ok 4
Fields: 5
Names: suid uid gid name environ
Null:  0 0 0 0 1
-16390 16390 16390 mon_role 
-16389 16389 16389 replication_role 
-16388 16388 16388 navigator_role 
-16387 16387 16387 sybase_ts_role 
-16386 16386 16386 oper_role 
-16385 16385 16385 sso_role 
-16384 16384 16384 sa_role 
-2 0 0 public 
-1 2 0 guest 
1 1 0 dbo 
2 3 0 probe 
ok 5
ok 6
ok 7
not ok 8
:
Server message number=208 severity=1 state=0 line=0 text=ok 9
ok 10
-16390 16390 16390 mon_role  
-16389 16389 16389 replication_role  
-16388 16388 16388 navigator_role  
-16387 16387 16387 sybase_ts_role  
-16386 16386 16386 oper_role  
-16385 16385 16385 sso_role  
-16384 16384 16384 sa_role  
-2   public  
-1 2  guest  
1 1  dbo  
2 3  probe  
ok 11
ok 12
ok 13
ok 14
ok 15
ok 16
ok 17
ok 18
ok 19
$VAR1 = [
          {
            'LITERAL_PREFIX' => '\'',
            'UNSIGNED_ATTRIBUTE' => undef,
            'MAXIMUM_SCALE' => undef,
            'MINIMUM_SCALE' => undef,
            'TYPE_NAME' => 'char',
            'INTERVAL_PRECISION' => undef,
            'NULLABLE' => 1,
            'CREATE_PARAMS' => 'length',
            'DATA_TYPE' => 1,
            'SQL_DATA_TYPE' => undef,
            'LITERAL_SUFFIX' => '\'',
            'CASE_SENSITIVE' => 1,
            'NUM_PREC_RADIX' => undef,
            'PRECISION' => 2048,
            'SEARCHABLE' => 3,
            'MONEY' => 0,
            'AUTO_INCREMENT' => undef,
            'LOCAL_TYPE_NAME' => 'char',
            'SQL_DATETIME_SUB' => undef
          },
          {
            'LITERAL_PREFIX' => '\'',
            'UNSIGNED_ATTRIBUTE' => undef,
            'MAXIMUM_SCALE' => undef,
            'MINIMUM_SCALE' => undef,
            'TYPE_NAME' => 'nchar',
            'INTERVAL_PRECISION' => undef,
            'NULLABLE' => 1,
            'CREATE_PARAMS' => undef,
            'DATA_TYPE' => 1,
            'SQL_DATA_TYPE' => undef,
            'LITERAL_SUFFIX' => '\'',
            'CASE_SENSITIVE' => 1,
            'NUM_PREC_RADIX' => undef,
            'PRECISION' => 2048,
            'SEARCHABLE' => 3,
            'MONEY' => 0,
            'AUTO_INCREMENT' => undef,
            'LOCAL_TYPE_NAME' => 'nchar',
            'SQL_DATETIME_SUB' => undef
          },
          {
            'LITERAL_PREFIX' => '\'',
            'UNSIGNED_ATTRIBUTE' => undef,
            'MAXIMUM_SCALE' => undef,
            'MINIMUM_SCALE' => undef,
            'TYPE_NAME' => 'unichar',
            'INTERVAL_PRECISION' => undef,
            'NULLABLE' => 1,
            'CREATE_PARAMS' => 'length',
            'DATA_TYPE' => 1,
            'SQL_DATA_TYPE' => undef,
            'LITERAL_SUFFIX' => '\'',
            'CASE_SENSITIVE' => 1,
            'NUM_PREC_RADIX' => undef,
            'PRECISION' => 2048,
            'SEARCHABLE' => 3,
            'MONEY' => 0,
            'AUTO_INCREMENT' => undef,
            'LOCAL_TYPE_NAME' => 'unichar',
            'SQL_DATETIME_SUB' => undef
          }
        ];
[download]

In t/main.t, change $DBI::err to $sth->err and see if that solves the problem.

We still have the weirdness that you don't get the message text, though.

Michael

Here's some info on error 208. Basically, it can't find the object that we created.

what is the EXACT version of your Sybase ASE, ASIQ or SQL Anywhere server that is in your $DSQUERY environment variable?

Jason L. Froebe

No one has seen what you have seen, and until that happens, we're all going to think that you're nuts. - Jack O'Neil, Stargate SG-1

The t/fail.t errors have to do with non-detected failure to insert a row into a table with declarative constraint. The test tries to insert a row that will violate the constraint and verifies that the correct error is raised. In this case the error is not raised.

The t/main.t error is also related to a forced failure. In this case the test is to try to select from an inexisting table which should return a 208 error code - but we don't get that error code.

In addition Bone_Scavenger has a problem with Sybase errors as seen by DBD::Sybase, in particular the text of the errors are not sent to the script.

At this point the only thing that I can think of is that there is some 64 bit mis-configuration of some sort that causes error codes (integers) in the C code to be mis-interpreted. I'm not really familiar with the Alpha platform, so I don't know if the compiler switches used make sense, or if there is a problem between the perl binary and the Sybase libraries.

Michael

Failed Test Stat Wstat Total Fail  Failed  List of Failed
----------------------------------------------------------------------
+---------
t/fail.t                  13    2  15.38%  7-8
t/main.t                  19    1   5.26%  8
[download]

The redefinitions may or may not be a problem. That's for mpeppler to determine (he's the author).

Hi,

When you extract the tar ball and run perl Makefile.PL you will be able to cd into the t directory that contains the tests. The files in there (*.t) contain the various tests for the perl module.

The test files are actually perl scripts that you can run directly if you so desire.

Jason