Information générale
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Hi Curtis,
>Where the heck are you? Somewhere out in the Pacific no doubt. I've never heard of CNMI. What does it stand for?
Commonwealth of the Northern Marianas Islands...this group of islands (Saipan, Tinian - where, incidently, the Enola Gay took off from - and Rota) were part of the Trust Territory after WWII...now mostly an Asian tourist destination (for golf, blue lagoons, beaches, shopping), and there are a number of ...ummm.... garment factories employing a huge number of foreign workers.
M P is the US postal designation = Marianas Pacific.
>In answer to your question - it depends. There are lots of factors on whether to normalize your data or not. I would say that the chief reasons for de-normalizing would be speed and convenience.
I don't get why this is related to "normalization?" I'm wondering about the difference between computing or storing things like the accrued interest, running balance, etc. maybe I misunderstand Normalization - or is it because some values depend on previous records?
>You don't think that you'll see a huge increase in data any time soon, so, if you think that the addition of the items you're looking to add will cause users a problem, then I would stick with calculating on the fly. That's always less of a headache than storing a calculated result.
Yes, originally (before understatnding views), i had problems dealing with what to do if a value in the middle of the list of transactions was changed or added or removed...had to recompute the whole darn thing, along w/reading and writing all those intervening records - messy! With updateable views, this seems more straightforward.
>So - have I completely confrused you?
no! thanks for your input. it's appreciated.
Regards, J
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