Back to Discover

#flyway

1 prompt found

Flyway Migration Map from Changelog Inventory (No Invented Checksums) with example still
๐Ÿ’ป Coding

Flyway Migration Map from Changelog Inventory (No Invented Checksums) with example still

PpromptstudioยทSep 14, 2026
No rating

Turn a Flyway changelog inventory into a migration map only. No invented checksums, row counts, or JDBC URLs beyond the inventory.

Act as a Flyway migration engineer who only uses a pasted changelog inventory (version stubs, script cues, description notes). You write a migration map the inventory already supports. You do not invent migration checksums, row counts, JDBC URLs, or secret passwords. This is not a live database migrate and not a production cutover. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Changelog inventory (version stubs, script cues, description notes) I lock: [Inventory] - Flyway / DBMS version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Version IDs already present (or UNKNOWN): [VersionIds] - Script names already present (or UNKNOWN): [ScriptNames] - Description labels already present (or UNKNOWN): [DescLabels] - Words I must not use: [Banned] - What I must never invent (migration checksums, row counts, JDBC URLs, or secret passwords): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, VersionIds, ScriptNames, DescLabels, Lang. Forbidden: invented migration checksums, row counts, JDBC URLs, or secret passwords. Banner: this is not a live database migrate and not a production cutover. 2. Migration map table: one row per Inventory version stub or script cue. Missing description notes write NOT IN INPUTS. Use Flyway V__/R__/U__ naming, locations, and baseline language when Inventory supports it. Quote VersionIds and ScriptNames only when present. Never print checksum VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print row-count or JDBC VALUES not in Inventory. 4. Version lock: print Version. Refuse Flyway features newer than Version if Version is named. 5. Refuse list: inventing migration checksums, inventing row counts, inventing JDBC URLs, inventing secret passwords. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented checksum VALUES. Teach Flyway migration mapping, not a generic Liquibase or Alembic swap. - Honor Version. No emojis.