DBIO-MSSQL

 view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

          MSSQL's DROP TABLE already removes the table's own indexes, the
          standalone DROP INDEX failed once the table was gone ("Invalid object
          name") and aborted apply()/upgrade(). DBIO::MSSQL::Diff::Index now
          receives the tables sections (threaded in by DBIO::MSSQL::Diff) and
          suppresses a standalone DROP INDEX for any index whose owning table is
          itself being dropped in the same pass. Indexes of surviving tables are
          still dropped as before; the two-argument diff() call stays backward
          compatible (absent table sections suppress nothing).

    * Tests
        - Add t/51-diff-drop-table-index-cascade.t and extend t/50-diff.t:
          full-diff regression for the DROP INDEX / DROP TABLE collision
          (karr #15) plus Diff::Index unit cases for the tables-aware drop
          suppression and its over-suppression guard.

    * Storage
        - new DBIO::MSSQL::Storage::ODBC (DBD::ODBC transport on top of the
          transport-neutral DBIO::MSSQL::Storage base). ODBC connections are now
          reblessed into this class instead of DBIO::MSSQL::Storage::Sybase, so
          the ODBC path no longer pulls in DBIO::Sybase. The Sybase class stays
          for the DBD::Sybase path. Needs DBIO core with the matching connector

MANIFEST  view on Meta::CPAN

t/00-load.t
t/08-shortcut.t
t/10-mssql.t
t/11-mssql-odbc.t
t/20-mssql-core.t
t/21-mssql-odbc-core.t
t/30-datetime-mssql.t
t/31-datetime-format.t
t/40-sqlmaker-mssql-torture.t
t/50-diff.t
t/51-diff-drop-table-index-cascade.t
t/52-introspect-contract.t
t/release-coverage.t
t/sqlmaker/limit_dialects/rno.t



( run in 1.134 second using v1.01-cache-2.11-cpan-e7c6538aa59 )