Kexi/Handbook/Introduction to Databases/Database Design: Difference between revisions
Corrected reference to other section |
No edit summary |
||
| Line 13: | Line 13: | ||
|prevpage=Special:MyLanguage/Kexi/Handbook/Introduction_to_Databases/Database_and_Spreadsheet | |prevpage=Special:MyLanguage/Kexi/Handbook/Introduction_to_Databases/Database_and_Spreadsheet | ||
|prevtext=Database and Spreadsheet | |prevtext=Database and Spreadsheet | ||
|nextpage=Special:MyLanguage/Kexi/Handbook/Introduction_to_Databases/Who_Needs_a_Database | |nextpage=Special:MyLanguage/Kexi/Handbook/Introduction_to_Databases/Who_Needs_a_Database | ||
|nexttext=Who Needs a Database? | |nexttext=Who Needs a Database? | ||
|index=Special:MyLanguage/Kexi/Handbook|indextext=Back to menu | |index=Special:MyLanguage/Kexi/Handbook|indextext=Back to menu | ||
Latest revision as of 22:08, 25 December 2024
Database Design
Database design needs careful planning. Note that Persons table redesign proposed in section Data integrity and validity can generate problems when the table is filled with data. For example, renaming a field is a simple task, but splitting the Address field into separate fields requires careful and tedious work.
To avoid such situations, rethink your database project before you create it in your computer, and before you and others will start to use it. Thus, by investing some time initially, you will most probably save your time on everyday use.