But the main point of the document is that just because you know how things 'must' be where you are, doesn't mean that every name you need to handle will be built on those same rules. I can think of cases which shows problems with most of those rules. The key is that each of the rules sounds like a rule that someone has assumed, and each of the rules is something that the author of the article know of (or at least can think of) a case where that rule doesn't hold. A rule that holds only 99.999% of the time is not always true.
On 11/9/19 9:44 PM, Doug wrote: > Au Contraire, Jens! In many local contexts you can normalize people's names. > I was born in Kansas, USA. My parents filled out a birth certificate for me. > It had a place on the form for first name, middle name, last name, and a > suffix like II or III. > > That birth certificate form determined that everyone born in Kansas (at that > time), had a first, middle, and last name. There was no discussion of the > matter. That's the way it was. The form led the way; people never thought > about whether it was effective or not. Each newly-born child was given a > first, middle, and last name. > > Effective was irrelevant for that system. There was no option, no > alternative. It simply was. > > All systems are like that at each moment in time. They are what they are at > any moment in time, and they force the users to behave the way the system > wants them to behave. If you want to change the system and momentum is on > your side, then immediately you have a new system - at that moment in time. > It is composed of the old system and the momentum. > > Back to names: just like the birth certificate, a system which assigns a name > to you, actually coerces you to have that name, because within that system, > you exist as that name. The "names" article is totally wrong when it says > that each assumption is wrong. Each of those assumptions is correct, and I > can find at least one system which makes each one correct. Within each > system, the assumption works, and is valid. > > My two cents... > Doug > >> -----Original Message----- >> From: sqlite-users <sqlite-users-boun...@mailinglists.sqlite.org> >> On Behalf Of Jens Alfke >> Sent: Saturday, November 09, 2019 5:11 PM >> To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> >> Subject: Re: [sqlite] Things you shouldn't assume when you store >> names >> >> On Nov 9, 2019, at 1:09 PM, sky5w...@gmail.com wrote: >>> In this case, data modelers hoping to save a column. arrggg. >>> It flies in the face of data normalization and pushes the >> problem down the >>> line. >> But you _cannot_ normalize people’s names; that’s the exact point >> of that article. Anything you assume about the structure of a name >> will be wrong in some culture. >> >> -Jens >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users@mailinglists.sqlite.org >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite- >> users > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users -- Richard Damon _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
