1
40%
main: 57%

Ran 15 Aug 2024 03:17PM UTC

Files 201

Run time 6s

Badge

Embed ▾

Committed 15 Aug 2024 03:01PM UTC coverage: 40.173% (+0.01%) from 40.163%

Job # 10406007516.1

Build Type

Pull #1089

github

Committed by

guggero

Commit Message

scripts+tapdb: do sqlc required replacement in script

Our SQL scripts on disk were neither SQLite nor Postgres compatible, we
used a version suited for sqlc to generate the correct data types we
wanted, then did some type replacements in-memory when actually applying
the migration files.
This is somewhat dangerous as it will lead to situations where if a user
applies a migration file manually, they'll end up with table primary
keys that ARE NOT auto incrementing.

To fix this issue, we make sure that we always write fully SQLite
compatible SQL code and only apply fixes for the sqlc code generation
directly before generating the code.

Pull Request Pull Request #1089: tapdb: fix multiple issues around migration file handling

Run Details

23689 of 58967 relevant lines covered (40.17%)

54330.91 hits per line

lightninglabs / taproot-assets / 10406007516 / 1
40%
main: 57%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job unit - 10406007516.1

lightninglabs / taproot-assets / 10406007516 / 1 40% main: 57%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job unit - 10406007516.1

lightninglabs / taproot-assets / 10406007516 / 1
40%
main: 57%

README BADGES
x