01 / DIRECT ANSWER
Back up before you open a mutation control
Load the intended offline state, press F9, open Features → Game Database and choose the exact table. Capture the full target row and a separate Career slot first. Make one edit, insert, clone or delete, then verify the primary key, related rows and row count after Career reload and—when persistence matters—game restart.
Table · PK · complete row · relations · backup.
Database changes apply automatically.
Same row · dependents · counts · restart.
02 / PRODUCT BOUNDARY
A live table surface—not a safe preset catalogue
Inspect tables and edit, insert, clone or delete records in the running offline tool.
No current official field dictionary, safe-ID catalogue or universal constraint validator is published.
Player, Team and Manager Editors own common football outcomes with a narrower blast radius.
The creator warns that incorrect changes can brick a Career save.
03 / RELATIONAL MODEL
A row is never just a line on screen
Unique identity inside its table. A clone must not keep the source PK.
A relationship to another owner. Copied values can become stale or wrong.
Other tables and game systems can turn one bad key into a wider failure.
EVIDENCE LIMIT: standard database docs define the concepts. The FC 26 Wiki confirms relational data and unique primary keys, but does not publish a complete field-level constraint map.
04 / BEFORE-MANIFEST
Five lines make an immediate save recoverable
05 / ORIGINAL INTERACTIVE EXPERIMENT
Mutate a synthetic schema—then prove the rollback
Use all four operations without touching FC 26. The lab records a before-state, applies the mutation immediately, produces an inverse instruction and compares deterministic checkpoint/current hashes.
RELATIONAL MUTATION LAB
02 / PARAMETERS
Edit one field
Checkpoint ready. No local mutations recorded.
03 / TABLE VIEW
| appointment_idPK | manager_idKEY | team_idKEY | role |
|---|---|---|---|
| 9001 | 301 | 10 | HEAD |
| 9002 | 302 | 20 | ACADEMY |
06 / CONTROLLED RESULTS
Seven tests separate a changed screen from a reversible result
Counts stable; inverse value restored the hash.
Row count +1; exact new PK gave a bounded inverse.
Training precondition rejected an existing identity.
Training precondition rejected an invalid relation.
Row copied; inherited keys remained visible for audit.
Full deleted row captured before removal.
Current serialization returned to checkpoint hash.
LIMIT: these are browser-lab results, not claims that Live Editor blocks the same invalid inputs. The hash is an equality signal, not a cryptographic Career signature.
07 / ROUTE & ANATOMY
Choose the table only after the correct offline state is loaded
- COLUMNS
- 137
- VALID RECORDS
- 21680
- IS PERSISTENT
- true
- SAVEGROUPS
- cmsquads, squads, pl
| # | CPY | DEL | EDIT | 🔑 playerid | field |
|---|---|---|---|---|---|
| 0 | ▣ | ⌫ | ✎ | 461822 | 48 |
| 1 | ▣ | ⌫ | ✎ | 460730 | 57 |
08 / CAREER PERSISTENCE GATE
Prove where the table lives before judging the edit
Record `IsPersistent`, savegroups and counts as clues—not a final guarantee.
The creator says tables visible in the Career file can be edited with Live Editor.
Reopen the Career and restart the game; compare the exact row and relations.
09 / COMMIT CONTRACT
“No confirmation needed” changes the safe order
NO PUBLISHED TRANSACTION: Confirm in the Insert dialog is not evidence of a staged, atomic or rollback-capable database transaction. No universal undo history is documented.
10 / EDIT FIELD OR ROW
Edit is the narrowest operation—if the owner is correct
Use Edit for the whole row or left-click one field. Prefer one field at a time. A stable visible value still does not prove it is the authoritative owner of the football outcome.
11 / INSERT ROW
A new row needs more than an empty ID
TABLE → INSERT ROWCTRL + NFILL FIELDS→CONFIRM- Prove the primary key is unused.
- Populate every required field with the correct type and range.
- Verify each referenced parent exists.
- Record the exact new PK before Confirm.
- Rollback by deleting only that inserted PK.
12 / CLONE ROW
Copy duplicates the hidden risk with the visible values
Identity + relations + defaults.
Collision until identity changes.
Fresh identity; every inherited key reviewed.
DO NOT STOP AT THE PK: a copied foreign key can be syntactically valid and still point to the wrong club, season, competition or owner.
13 / DELETE ROW
Delete the child only when you can name every dependent
No known dependents; full row captured.
Many readers; dependency map incomplete.
Potential orphaned relations and unloadable Career.
SAFEST REVERSAL: if the dependency graph is incomplete, restore the pre-edit Career copy. Recreating a visible row may not reconstruct every relationship.
14 / KEYS & RELATIONS
Validate identity, reference and meaning separately
No other row in the table owns it.
The referenced parent row is present.
The valid parent is actually the intended club/player/event.
Find rows and systems that read this identity.
15 / SYSTEM PRECEDENCE
A table value can be valid and still lose
The creator’s VPRO guide provides a concrete example: development-tree attributes can override the `players` table for the managed-team VPRO. Unsupported league/team removal is separately documented as hard-coded and not fixable through database tables. Route the outcome to its owner.
16 / ROLLBACK LADDER
Use the smallest recovery that proves the original state
Same PK, captured old value.
Only when no dependents were created.
Only with complete relations and fields.
Restore a separate known-good slot.
17 / FAILURE DIAGNOSIS
Classify the failure before making a second edit
Inspect the Career in RDBM25; do not loop the same mutation blindly.
Reproduce the triggering event and route to the specialist surface.
Audit PK, fields, types, ranges and parent keys.
Compare every key against the intended new owner.
Stop, preserve evidence and restore the separate backup.
Check dedicated editor, legacy asset, Lua/runtime or hard-coded boundary.
18 / VIDEO AUDIT & TOOL IDENTITY
Most “database editor” videos are about a different product
No current FC 26 video documented all four row operations, relational preconditions, persistence and rollback. The strongest long Live Editor walkthrough is legacy FC 25.
This guide.
Persistence inspection.
Different build-time product.
Different execution surface.
19 / ADVANCED QUESTIONS
Database Editor FAQ
01Where is Database Editor in FC 26 Live Editor?+
Run a compatible Live Editor with the intended offline game state loaded, press F9, then open Features → Game Database and choose the exact table.
02Does Database Editor save changes automatically?+
Yes. The official Wiki says changes in this editor are saved automatically and need no separate confirmation. Treat each mutation as immediate.
03Does automatic save mean my change survives a restart?+
No. Only some tables are stored in a Career file; other tables reset when the game restarts. Automatic mutation and durable persistence are different claims.
04How can I tell whether a table is stored in my Career?+
The creator recommends opening the Career file in RDBM25. Tables visible there can also be edited with Live Editor. Then prove the exact row with a reload.
05How do I insert a new row?+
Open the table, choose Table → Insert Row or press Ctrl+N, fill the fields and choose Confirm. First prove the primary key is unused and every required relation is valid.
06How do I clone a row safely?+
Use Copy on the source row, assign a new unique primary key, then inspect every copied key and relationship. A fresh PK alone does not make copied relations correct.
07Can I delete a row and undo it later?+
The public guide does not promise an undo stack. Capture the full row and dependent relationships first; for an unknown blast radius, restore a separate Career backup.
08What happens if two rows use the same primary key?+
The creator explicitly says primary keys must be unique. Do not test a collision in your only Career; resolve the ID before committing the row.
09Does Live Editor validate foreign keys and field ranges?+
No complete validation contract is published. Check the schema, required fields, types, ranges and related rows yourself before a mutation.
10Why did a database value change back?+
The table may be non-persistent, or another game system may own and overwrite the value. Isolate whether restart or a specific game event triggers the reversal.
11Is the interactive lab connected to FC 26?+
No. It is a deterministic browser-only training dataset. Its guards demonstrate preconditions; they are not promises about Live Editor validation.
12Can I use this online or on console?+
No. This guide is for the Windows PC offline tool. FUT, Clubs, online play and console save editing are outside scope.
20 / EVIDENCE LEDGER
Procedure, database theory and audience intent stay separate
Reviewed 18 August 2026. The creator Wiki, repository, changelog, releases and manifest control product claims. Standard database docs define relational terminology. Videos provide context only.
Current creator procedure for edit, insert, clone, delete, automatic saving and persistence limits.
Product boundary and Database Editor capability.
Current FC 26 editor chronology and feature context.
Creator-controlled release history.
Current editor/game compatibility snapshot.
Launch, offline and F9 prerequisites.
Published table, field, row, insert, delete and edit semantics for the separate legacy scripting surface.
Current Lua generation and improved database-operation context.
Concrete example of a higher-priority system overriding a players-table value.
Hard-coded behavior boundary outside ordinary database edits.
Current field-write defect report for Lua; incident evidence, not GUI behavior.
Career-table inspection tool linked by the creator.
Primary-key, foreign-key and referential-integrity terminology.
Transaction and rollback terminology; not a claim about Live Editor.
Historical FC 25 anatomy reused by the current Wiki.
Table menu and Ctrl+N evidence.
Field-value editor plus Confirm/Cancel anatomy.
Per-row clone control.
Per-row destructive control.
Per-row edit control.
Single-field edit interaction.
FC 25 navigation vocabulary only; not current authority.
Current audience intent; not a database procedure.
FC Editor Tool workflow retained to explain product separation.