identifier
4 identifier types: 3 a sibling also accepts and reads alike, 1 that decompose into parts, 2 in Meridian's open data.
The 4 identifier types
Each type's first registry sample, against every sibling's rule
| Type | Sample | Also accepted by |
|---|---|---|
Increment / Counter increment · BIGINT | 1 | numeric_code |
Numeric Code numeric_code · VARCHAR | 840 | increment |
UUID uuid · UUID | 550e8400-e29b-41d4-a716-446655440000 | alphanumeric_id |
Alphanumeric Identifier alphanumeric_id · VARCHAR | SKU-12345 | — |
Which identifier type is it?
2 of 4 identifier types accept it, and read it alike.
| Type | Reads it as |
|---|---|
Increment / Counter increment | 1 |
Numeric Code numeric_code | 1 |
In Meridian's open data
- Alphanumeric Identifiergleif
.legal_form - Numeric Codeedgar
.cik
How the engine tells them apart
- Increment / Counter — Difficult to distinguish from regular integers without column context.
- Numeric Code — Column-level disambiguation (header hints, consistent length, leading-zero presence) differentiates from plain integer_number.
Use it
CLI · DuckDB
$ printf '%s\n' '1' '2' > column.txt
$ finetype infer -f column.txt --mode column
SELECT ft_profile(v) FROM (VALUES ('1'), ('2')) t(v);After 2, 2 types remain: increment, numeric_code.