in reply to Re: Errors during "make test" of DBD::Sybase
in thread Errors during "make test" of DBD::Sybase

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 } ];

Replies are listed 'Best First'.
Re^3: Errors during "make test" of DBD::Sybase
by mpeppler (Vicar) on Oct 16, 2004 at 05:50 UTC
    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

      Sorry, was off all day Monday and Tuesday morning.

      You wanted me to do this, right?

      else { print "ok 7\n"; ($sth->err == 208) and print "ok 8\n" or print "not ok 8\n";

      Same result - "not ok 8"

        Michael had an offline discussion with someone from Sybase. They suggested that I try building the "firstapp" Open Client sample program and change the select to a non-existent table (to trigger a 208 error), to see if I get the msg text. I did that, and here's the output:
        Server message: number(5701) severity(10) state(2) line(0) Server name: SQLLAM01 Changed database context to 'master'. Server message: number(208) severity(16) state(1) line(1) Server name: SQLLAM01 pubs2..authors not found. Specify owner.objectname or use sp_h +elp to check whether the object exists (sp_help may produce l.
        Since I see the message text, I'm guessing that my Open Client installation is working fine. Does that mean it's a Perl or DBI::Sybase problem?

        Thanks.

Re^3: Errors during "make test" of DBD::Sybase
by jfroebe (Parson) on Oct 15, 2004 at 20:06 UTC
    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 208 error is expected. What is not expected is that the script doesn't see it. I now see that this might be a bug in the test script.

      What is NOT expected at all is that he is not getting any of the error messages:

      Server message number=208 severity=1 state=0 line=0 text=ok 9
      Note the last bit there - it should say something like:
      text=sys_users not found. Specify owner.objectname or use sp_help...
      Michael
      select @@version output:

      Adaptive Server Enterprise/12.5.0.3/EBF 11338 ESD#3/P/Compaq Tru64/OSF1 V5.0A/rel12503/1933/64-bit/FBO/Fri Aug 1 04:54:12 2003