datatug / datatug-cli / 38875207611
100%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 553
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
38875207611

push

github

web-flow 
fix(db): follow-ups to the MySQL SQL-script export (review of #421) (#425)

Follow-up to #421, fixing the findings of the independent review (https://github.com/datatug/datatug-cli/pull/421#issuecomment-6209534390). Binding rule: a name is renamed only when MySQL cannot store it, always with a counted warning.

Source commits:

- 8cc97668fb5e fix(db): follow-ups to the MySQL SQL-script export (review of #421)
  M1 columns are renamed only when MySQL rejects them (case, not accents); M2 strict query parsing and repeated parameters; M3 the verifier compares default values and check expressions; M4 a REAL in a text column is SQLite's own text. Also: header validation, key-values-collide, values-normalized for REAL in DECIMAL, umask and no-hard-link file creation, workflow path filters, exit codes.
- 67f7f0e221ec fix(db): FK names compared like MySQL, digest-only key scan, stricter verifier
  FK names fold accents and ß as MySQL 8.4 does (whole BMP checked against the server); check names are unique schema-wide and apart from key names; the key-collision scan keeps 16 bytes a row; the verifier checks the REGEXP_LIKE match type, that SQLite's text of a REAL reads back, and the rename gate uses MySQL's fold; the fallback copy removes only the file it made.

Pull request: datatug/datatug-cli#425
Review: https://github.com/datatug/datatug-cli/pull/425#issuecomment-6211430657

71011 of 71012 relevant lines covered (100.0%)

1.01 hits per line

Jobs
ID Job ID Ran Files Coverage
1 38875207611.1 553
100.0
GitHub Action Run
Source Files on build 38875207611