Subject | Re: avoiding duplicates |
---|---|
Author | Svein Erling Tysvær |
Post date | 2005-07-12T13:38:29Z |
--- In firebird-support@yahoogroups.com, Jason Dodson wrote:
to address them with their properly cased name and you cannot simply
have the first letter with capital letters, because mr Donald McDuck
would be furious if you wrote Donald Mcduck. Moreover, with a database
of several million names, you would want to avoid natural searches as
much as possible. In such situations, I do not consider UPPERcased
fields much more redundant than primary keys without business meaning
(i.e. created through generators). UPPERcased fields populated and
maintained through triggers are in some situations almost vital in
Firebird.
Just my opinion,
Set
> Anyway, the very term "Normalization" means "the process of removingAssume a case sensitive collation. Having lots of customers, you want
> redundant data from your tables in order to improve storage
> efficiency, data integrity and scalability". Having an UPPERized
> field is redundant data. It has no extra value other then it saves
> you from doing work in your application.
to address them with their properly cased name and you cannot simply
have the first letter with capital letters, because mr Donald McDuck
would be furious if you wrote Donald Mcduck. Moreover, with a database
of several million names, you would want to avoid natural searches as
much as possible. In such situations, I do not consider UPPERcased
fields much more redundant than primary keys without business meaning
(i.e. created through generators). UPPERcased fields populated and
maintained through triggers are in some situations almost vital in
Firebird.
Just my opinion,
Set