(D9) Additional schema fields

Totally no time in the queues, so this slipped off my radar.

There are some feature requests that need field schema changes, so are there any merit in the following feature requests??

If so, we need to get these in now as there are no supported field schema changes, so whatever is defined now must last to the end of the D8 development cycle!!!!

Possible to store language specific settings (well the name types that are language specific)

For gender based languages, this would involve a language field (eg: spanish)

And maybe expose this to the users at the form level to switch forms similar to address field module & country

So a smallint or small varchar for the gender and another for the language type or und (site default)

Surname / Family name prefixes

Slightly complicated one, not sure on the best approach: #1184618: Better support for family name prefixes →

Almost thinking a new column / field ?? Maybe hidden on the widget itself, but on load combine / on save split.

Codes:

f, e, E use the combined values of both fields
z changes to use the family field only

New codes:

p for the prefix
h for the surname without the prefix (or another letter, the obvious ones are already taken)

Ordering / Search

A few issues include, no simple search ordering, family name prefixes, ...

I was considering adding a new search field index, where this would automatically populate on save to a predefined format:

Maybe new required format (or a preset user defined one):

Name: Search
Code: search
Format: U(((f-i)+ig)+im)

And a trimmed hidden field that stores this in the database, with transliteration support to convert to plain ASCII

Uppercase A to Z #65 - #90, Space is #32, so:
* searches can be implode('%', explode(' ', $string)) with the defined format for quick easy searching.
* ordering can be based off a single db column
a a
a b
aa a
aa b

Or just the column itself and alter hooks to allow other modules to interact with this.