Hi Louis,
the schema can certainly accomodate the storage and search needs for your case. However, the best way to display such scenarios should be up for debate.
Let's say we have Mary born Smith, married Jones, then McDonald, then Williams, then White, then Miller.
"Smith-1111", "Mary", "Mary", English-FK, FirstName-FK, 1
"Smith-1111", "Smith", "Smith", English-FK, MaidenName-FK, 3
"Smith-1111", "Jones", "Jones", English-FK, LastName-FK, 4
"Smith-1111", "McDonald", "McDonald", English-FK, LastName-FK, 5
"Smith-1111", "Williams", "Williams", English-FK, LastName-FK, 6
"Smith-1111", "White", "White", English-FK, LastName-FK, 7
"Smith-1111", "Miller", "Miller", English-FK, LastName-FK, 8
So the above would get displayed as Mary Smith Jones McDonald Williams White Miller. This is essentially a gibberish. However, the schema itself is flexible enough and can permit introduction of new name types without modification of the user interface. So, after much debate WikiTreers may agree that such a case should be handled by new name type "SeparatedName". Then the name parser module that displays name can be extended to format such values with a preceding blurb such as "formerly known as" or "divorced surname", etc.
Then the data entered in the following way:
"Smith-1111", "Mary", "Mary", English-FK, FirstName-FK, 1
"Smith-1111", "Smith", "Smith", English-FK, MaidenName-FK, 7
"Smith-1111", "Jones", "Jones", English-FK, SeparatedName-FK, 3
"Smith-1111", "McDonald", "McDonald", English-FK, SeparatedName-FK, 4
"Smith-1111", "Williams", "Williams", English-FK, SeparatedName-FK, 5
"Smith-1111", "White", "White", English-FK, SeparatedName-FK, 6
"Smith-1111", "Miller", "Miller", English-FK, SeparatedName-FK, 2
Mary Miller formerly known as Jones, formerly known as McDonald, formerly know as Williams, formerly known as White, nee Smith.
The thing is that while geneaologists will debate about the proper way to display the data it will already be stored in the database in way that is flexible enough to allow future presentation changes while already fully supporting the search functionality that can be build to use individual name fields.