Lance,
The first thing to note is that for more recent DBD::ODBC's a newer OOB is
required to pass all of the 20SqlServer tests (I know you didn't get that far
but when you do mail me personally and I'll send you the most up to date OOB
client for Linux). The tests that sometimes fail with OOB client 1.0.0.40 and
before are 20SqlServer 7-9, 13-18, 20, 23-25. Having said that, not many people
are likely to be doing all of the stuff in the 20SqlServer test.
Secondly:
[1] Can you confirm exactly what OOB client and server you have?
cat /usr/local/easysoft/oob_install.info will do on the client and browsing
http://mywindowsmachine:8890 will say at the top of the page the server
version.
[2] Can you send me an OOB client trace.
You can get an OOB client trace by creating an odbc.ini file in the
directory where you are running make test for DBD::ODBC from.
Create the odbc.ini and put in it:
{Settings}
Logging = 0xffffff
Note they are curly braces. Now when you run make test you will get one or
more files in /tmp called esoobclient.log_<PID> where <PID> is the process
ID. Send those to me.
> DBD::ODBC::st fetchrow failed: [unixODBC][][Microsoft][ODBC SQL Server
> Driver]String data, right truncation (SQL-01004)(DBD: st_fetch/SQLFetch
> (long truncated) err=-1) at t/ODBCTEST.pm line 56.
That is a fetch on a SQLGetTypeInfo call which would be strange to get a
string data truncation error for - this is one of the reasons I'd like to see
the OOB client logs.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 11-Dec-2002 Lance Wilson wrote:
> Platform: RedHat 7.3
> DBI: Latest Version
> DBI::ODBC: Version 1.0
> Using the EasySoft ODBC Bridge as the transport to the Microsoft Server...
> latest version.
>
> I already have the ODBC bridge working correctly, tested, should be fully
> ODBC 3.0 compliant, etc.
>
> No problems installing the DBI Software at all.
>
> When I do 'make test' I get the following errors.... any suggestions as to
> the cause? Do I need to make a change as to what the MS SQL server replies
> with???
> -------------------------------------------------------
> [lance@alyssa DBD-ODBC-1.00]# make test TEST_VERBOSE=1
> PERL_DL_NONLAZY=1 /usr/local/bin/perl "-MExtUtils::Command::MM" "-e"
> "test_harness(1, 'blib/lib', 'blib/arch')" t/*.t
> t/01base............1..5
> ok 1
> ok 2
> ok 3
> ok 4
> ok 5
> ok
> t/02simple..........1..17
> ok 1
> Test 2: connecting to the database
> ok 2
> Test 3: create test table
> DBD::ODBC::st fetchrow failed: [unixODBC][][Microsoft][ODBC SQL Server
> Driver]String data, right truncation (SQL-01004)(DBD: st_fetch/SQLFetch
> (long truncated) err=-1) at t/ODBCTEST.pm line 56.
> DBD::ODBC::st fetchrow failed: [unixODBC][][Microsoft][ODBC SQL Server
> Driver]String data, right truncation (SQL-01004)(DBD: st_fetch/SQLFetch
> (long truncated) err=-1) at t/ODBCTEST.pm line 56.
> Unable to find a suitable test type for field COL_C at t/ODBCTEST.pm line 63.
> dubious
> Test returned status 255 (wstat 65280, 0xff00)
> DIED. FAILED tests 3-17
> Failed 15/17 tests, 11.76% okay
> t/03dbatt...........1..16
> ok 1
> ok 2
> DBD::ODBC::db do failed: [unixODBC][Microsoft][ODBC SQL Server Driver][SQL
> Server]Invalid object name 'PERL_DBD_TEST'. (SQL-42S02)(DBD: Execute
> immediate failed err=-1) at t/03dbatt.t line 112.
> Use of uninitialized value in numeric lt (<) at t/03dbatt.t line 38.
> Use of uninitialized value in numeric eq (==) at t/03dbatt.t line 39.
> ... etc.
>
>
> /'^'\
> ( o o )
> -----------------------------------------oOOO--(_)--OOOo----
> Lance Wilson
> President- WebGuy Internet, Inc. .oooO
> EMail: [EMAIL PROTECTED] ( ) Oooo.
> -------------------------------------------\ (----( )-----
> \_) ) /
> (_/
--
Martin J. Evans
Easysoft Ltd, UK
Development
