Check, optimize, and publish managed data

Validate

Choose the managed dataset type

Select Imported dataset or Converted dataset, find the snapshot by name, and run validation. The report summarizes errors and warnings and groups issues by table and field where possible.

• Imported snapshots are checked against their detected FIFA edition.
• Converted snapshots are checked against their target FIFA edition.
• Validation does not modify or repair the snapshot.
• Run the report again after replacing or recreating problematic data.

Playernames

Close ID holes or remove unused names

Choose an imported or converted snapshot, then select Minimize, Remove unused, or both. Combined runs remove unreferenced playernames and dcplayernames rows first, then assign contiguous IDs and rewrite firstnameid, lastnameid, playerjerseynameid, and commonnameid references in players.

Before the run, one control-free canvas shows playernames and dcplayernames in separate rows on a shared ID axis. Matching IDs align across rows, headline totals sum both tables, disjoint schema ranges are placed next to each other without inventing holes in the invalid numeric gap, and editions without dcplayernames show one row. The canvas distinguishes occupied runs, active-span holes, remaining capacity, and IDs outside each table’s published FIFA range. Drag horizontally to pan, pinch or use Ctrl/Cmd plus the wheel to zoom, and double-click to reset. Hover or use the arrow keys to inspect a table row and contiguous run. If strict validation finds duplicate or ambiguous references after profiling, the chart remains available for diagnostics while operations stay blocked. Dataset details retain the same before-and-after Playernames views, while their live inspection shows separate cards only for fifatables-supported tables. Preserved unsupported text files remain listed through the import warning instead of appearing as table cards.

Overwrite the selected application-managed dataset after confirmation or save a new entry in Converted datasets. Both choices produce a complete DB Master text snapshot, including unaffected and otherwise unsupported text tables.

• Overwrite changes only the selected managed copy; original external sources are never modified.
• Managed names must be unique and no longer than 80 characters.
• Minimize repairs referenced integer IDs outside the published range when capacity permits; Remove unused alone requires IDs to already be in range.
• Missing or ambiguous references, duplicate or invalid IDs, and range-capacity overflow stop the operation.
• Copy-on-write installation leaves the existing managed snapshot active after failure or cancellation.
• Overwriting a managed t3db import converts its application-owned representation to text while preserving its original t3db provenance.

Export

Select a converted dataset and destination

Choose an available converted dataset and a parent destination folder. QDB Converter creates a uniquely named child folder, writes the complete snapshot, and offers Reveal in folder when the export succeeds.

1. Select the converted dataset.
2. Choose the parent output folder.
3. Review the destination summary.
4. Export and reveal the resulting child folder.

Text contract

Write deterministic DB Master text

Each table uses target-schema field order, a UTF-16LE byte-order mark, tab separators, CRLF line endings, and DB Master-compatible quoting. Repeated exports create new folders rather than overwriting earlier output.

Safety

Keep managed and external files independent

Deleting a converted or Playernames result later removes only its application-owned managed copy. Previously exported folders remain where you created them.