datatug / datatug-cli / 38880692773
100%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 561
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 99.999%. Remained the same
38880692773

push

github

web-flow 
feat(db): write a SQL Server SQL script from SQLite with db copy --to sqlscript://...dialect=mssql (#427)

Stage 2 of the multi-dialect SQL-script export: **SQL Server**. `datatug db copy --from sqlite://x.sqlite --to 'sqlscript:///out.sql?dialect=mssql'` writes a deterministic T-SQL script (stage 1, MySQL, is #421). The dialect key is `mssql`; the demo-db site's format key for the same output is `sqlserver` (documented in `docs/db-copy.md`). There is no public verify command: the verifier is still `internal/crossverify`.

Source commits:

- 12a129733e0e feat(db): write a SQL Server SQL script from SQLite with db copy --to sqlscript://...dialect=mssql
  Adds the mssql dialect to the SQL-script export: one transaction of GO batches, each guarded so a client that continues after an error runs nothing outside the transaction, UTF-8 with a byte order mark loaded with sqlcmd -i, bracket-quoted names kept byte for byte, NVARCHAR/DATETIME2/DECIMAL/BIT/IDENTITY types, a static cascade-path analysis, one type per foreign key class, key size budgets, filtered unique indexes for keys over NULLs, and a SQL Server verifier in internal/crossverify (go-mssqldb replaces the deprecated denisenkom driver). A separate non-required journey workflow loads every script into a digest-pinned SQL Server 2022 container.
- 006f734693d8 docs(db): say which Sakila keys lose their ON UPDATE action on SQL Server
- 9735a03a7a51 fix(db): report the final FK-class type, state exactly which SQL Server name merges the export misses
  The type-widened warning for a foreign key class now names the type after the key budgets (it said NVARCHAR(11) for a column created as NVARCHAR(255)); docs say which names SQL Server's default collation merges that the export does not catch (ß/SS, full-width), why -b matters, what the verifier does not compare, the marker-name case rule and the D10 record.
- 93ce352936b2 fix(db): run the MySQL-only verifier checks per engine; SQL Server header validation, ... (continued)

72262 of 72263 relevant lines covered (100.0%)

1.01 hits per line

Jobs
ID Job ID Ran Files Coverage
1 38880692773.1 561
100.0
GitHub Action Run
Source Files on build 38880692773