Recognises a truncated identifier taken as the real name
A header warning that a name was over the target's limit and was emitted with an 8-character hash suffix. The hashed form is the name in the database, and it is what appears in the constraint-violation message that operations has to interpret at 3am.
Can AI do this?
People still lead Few or none of the tested AI models showed they master this. 0 of 10 models master it.
| Model | Tier | Probability of mastery | Status |
|---|---|---|---|
| gemini-4-argon | Flagship | 19% | Not shown |
| gemini-3.1-pro-preview | Flagship | 19% | Not shown |
| gpt-6-astra | Flagship | 20% | Not shown |
| claude-fable-5-1 | Flagship | 21% | Not shown |
| gemini-3.8-flash | Mid tier | 22% | Not shown |
| gpt-6.1-sol | Mid tier | 21% | Not shown |
| claude-sonnet-5-5 | Mid tier | 19% | Not shown |
| gemini-3.5-flash-lite | Low cost | 22% | Not shown |
| gpt-6-luna | Low cost | 20% | Not shown |
| claude-haiku-5-5 | Low cost | 21% | Not shown |
Mastered means a probability of at least 90% that the model has this knobit, estimated from its graded answers. “Not shown” means the answers do not settle it either way. How the models are tested.
What it looks like in practice
Expected result: The real database name and the model change avoiding it
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: Oracle 11g target (--oracle-max-identifier 30); ix_fact_payment_account_key_value_date_key_status_code emitted as ix_fact_payment_accou_a91c4f2e, which exists in no document anyone can search Acceptable: conventions.abbreviations in model-config.yaml applied consistently (acct, val, sts — never sometimes one and sometimes another) and the name shortened in the model until the warning is gone (PHY-010)
Also known as: Truncated identifier taken as the real name (generated DDL)
Related knobits
Builds on
All 33 knobits of Generate and review DDL.
Source: Review checklist 08-ddl, row 10; this skill (08-ddl.md)