I\'m designing a contact manager/address book-like application but can\'t settle on the database design.
I know that normalization has been extensively discussed on Stack Overflow. I\'ve read many of the previous discussions. I\'ve got some additional questions though.
I\'ve never used triggers before, but this seems like a solid use case. I\'d like to know if triggers are what I should be using, and if so, I could use a little hand-holding on how to go 开发者_开发技
Can Oracle Materialized views be used to join multiple related tables having foreign keys to create a larger denormalized big table which is refreshed instantaneously?
I have a table with the following structure: WorkerPersons ------------------------------- ID(PK) PersonID(Indicates which version of Person the record describes)
I have the following locations table: ---------------------------------------------------------- ID | zoneID | storeID | address | latitude | longitude |
One of my queries can take a lot of different filters and sort orders depending on开发者_C百科 user input. This generates a huge index.yaml file of 50+ indexes.
Here is the situation: [Job] belongs to one [Job Category], which [Job Category] is belong to one [Industry]
I\'ve built a rating system for movies in MySQL, howeve开发者_开发问答r the concern is that when my query sums up all the ratings and divides it, it might have to sum up millions and millions of recor
this time I got a more general question. Should I use multiple views rather than stored procedures for weighted a开发者_Python百科ggregation of data, if the original data is updated periodically?
加载中,请稍侯......