| T O P I C R E V I E W |
| crissand |
Posted - 19 Nov 2005 : 21:55:06
As a database specialist I'd like to suggest a major modification of XMM database, that will avoid redundancy and will make the database smaller.
The idea is: considering the table movies as the main table, all the other informations from there to be replaced by pointers to the other tables. Example:
Movie title: Gia, stored in "movies" table.
Actor: name: Angelina Jolie (Voigt), index: 3. The name and index to be stored together with other information about the actor in "actors" table and in the main table will be stored only the index 3.
And so on.
That way "movies" table will shrink a lot, and the other tables will be reused. Another example:
Movie title: Girl, Interrupted, stored in "movies" table.
Actor index 3, from "actors" table will be the same Angelina Jolie.
I know it's a lot to work to redefine the tables and the relations but I guess it's much reliable and will use less memory.
What do you think? |
| 2 L A T E S T R E P L I E S (Newest First) |
| crissand |
Posted - 23 Nov 2005 : 19:36:39
I'm sure it will be a major modification, since there will always have to deal with more than one table. But the size of the database will shrink a lot, because of the elimination of redundancy.
Actually, if the name of the fields from forms and reports it will be the same, only the queries will have to be rewritten. And some index to add to each table. |
| Alessio Viti |
Posted - 22 Nov 2005 : 21:51:15
Hi Crissand,
Thank you very much for your suggestions! I have build the XMM database some years ago, this is why is not so "good". I have in mind to change the structure in future, but this take very much work for change the code inside XMM.
Thank you again,
Alessio |
|
|
