text
4 text types: none a sibling also accepts, 1 that decompose into parts, 3 in Meridian's open data.
The 4 text types
Each type's first registry sample, against every sibling's rule
| Type | Sample | Also accepted by |
|---|---|---|
Emoji emoji · VARCHAR | 😀 | — |
Entity Name entity_name · VARCHAR | The Olive Garden | — |
Plain Text plain_text · VARCHAR | This is a plain text description | — |
Single Word word · VARCHAR | hello | — |
Which text type is it?
1 of 4 text types accepts it.
Entity Name and Plain Text carry no pattern or format, so they have no rule to ask.
| Type | Reads it as |
|---|---|
Emoji emoji | 😀 |
In Meridian's open data
- Entity Namegleif
.legal_nameedgar.company_nameedgar_gleif.company_nameedgar_gleif.legal_name - Plain Textnaics
.titlenaics.descriptionhts.descriptionhts.description_fullhts.section_titlehts.general_ratehts.special_ratehts.column2_ratehts.quota_quantityhts.additional_dutiesschedule_b.descriptionschedule_b.description_fullschedule_b.description_shortschedule_b.section_titlehcpcs.descriptionhcpcs.description_fullhcpcs.short_description - Single Wordgleif
.registration_statusedgar.exchangenaics.leveledgar_gleif.key_typeedgar_gleif.categoryedgar_gleif.reg_statusedgar_gleif.methodedgar_gleif.tierhts.levelhts.text_sourcehts.sectionschedule_b.levelschedule_b.text_sourceschedule_b.sectionhcpcs.levelhcpcs.text_sourcehcpcs.action_codehcpcs.coverage_codehcpcs.multiple_pricing_indicatorhcpcs.asc_payment_group
Use it
CLI · DuckDB
$ printf '%s\n' '😀' '🎉' > column.txt
$ finetype infer -f column.txt --mode column
SELECT ft_profile(v) FROM (VALUES ('😀'), ('🎉')) t(v);After 🎉, one type remains: emoji.