Information générale
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Mike:
> its not present in my apps, so I'm happy.
I believe this is a common reaction on UT and it is often the source of
my frustation/reaction.
People naturally want to repeat what has worked for them before. This is
fine with me but it's not argument enough to say other considerations
should be discarded. People do all kinds of applications and unless I
know a lot about what they are doing (Nadya in my case), I tend to give
them options instead of stating what has worked for me. Of course this
does not apply to all situations. A technical question can often be
answered by one answer without stating alternatives or the pros and cons
of such a method. My main problem occurs in threads like "Surrogate vs
Natural keys", "Forms as Forms vs Forms as Classes" where there are several
individual that post holy truths. IMO, this is a disservice to the
UT community because it can really influence a newcomer to stop thinking
about other possible solutions (the worst habit a person can have after
smoking of course < bg >). I don't want to be maimed or killed by a
product whose designer blindly applied solutions from the past. I don't
want to imply they do apply, just that their appropriatness should be verified
before implementing them.
Daniel
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement