view release on metacpan or  search on metacpan

README  view on Meta::CPAN

2. Full details of which software you are using, including:

  Perl version (the output of perl -V)
  ODBC Driver and version
  ODBC Driver manager used and version

It is important to check that you are using the latest version before
posting. If you're not then I'm *very* likely to simply say "upgrade to
the latest". You would do yourself a favour by upgrading beforehand.

Please remember that I'm _very_ busy. Try to help yourself first,
then try to help me help you by following these guidelines carefully.

Regards,
Tim, Jeff and Martin.

===============================================================================
Other info:

DBI 'home page': http://dbi.perl.org

t/70execute_array_native.t  view on Meta::CPAN

        $has_test_nowarnings = 0;
        plan skip_all => 'MS Access does not support array operations';
    }
    if ($driver_name =~ /sqlite/) {
        $has_test_nowarnings = 0;
        plan skip_all => "SQLite fails this test horribly - I can't find anywhere to report it";
    }

    diag("\n\nNOTE: This is an experimental test. Since DBD::ODBC added the execute_for_fetch method this tests the native method and not DBI's fallback method. If you fail this test it probably means the ODBC driver you are using does not have suffi...

If this test fails it should not stop you installing DBD::ODBC but if it fails with an error other than something indicating 'connection busy' I'd strongly suggest you don't set odbc_array_operations and stick with DBI's default implementation.

If this test fails for your driver I'd like to hear about it so I can compile a list of working drivers and perhaps pass bug reports on to the maintainers. Please rerun this test with TEST_VERBOSE set or using prove and send the results to the dbi-us...

    diag("\n");
    diag("Perl $Config{PERL_REVISION}.$Config{PERL_VERSION}.$Config{PERL_SUBVERSION}\n");
    diag("osname=$Config{osname}, osvers=$Config{osvers}, archname=$Config{archname}\n");
    diag("Using DBI $DBI::VERSION\n");
    diag("Using DBD::ODBC $DBD::ODBC::VERSION\n");
    diag("Using DBMS_NAME " . DBI::neat($dbh->get_info(17)) . "\n");
    diag("Using DBMS_VER " . DBI::neat($dbh->get_info(18)) . "\n");

test_results.txt  view on Meta::CPAN

# N.B. Some drivers (postgres/cache) may return ODBC 2.0 column names
for the SQLTables result-set e.g. TABLE_QUALIFIER instead of TABLE_CAT
t/03dbatt...............ok
t/05meth................ok
t/07bind................ok
t/08bind2...............ok
t/09multi...............ok
t/10handler.............ok
t/12blob................ok
t/20SqlServer...........ok 54/65# DBD::ODBC::st execute failed:
[unixODBC][Microsoft][ODBC SQL Server Driver]Connection is busy with
results for another hstmt (SQL-HY000) at t/20SqlServer.t line 202.
# DSN=dbi:ODBC:DSN=XXX;MARS_Connection=yes;
#
# NOTE: You failed this test because your SQL Server driver
# is too old to handle the MARS_Connection attribute. This test cannot
# easily skip this test for old drivers as there is no definite SQL Server
# driver version it can check.
#
t/20SqlServer...........ok
        1/65 skipped: WARNING: driver does NOT support MARS_Connection