Kexi/Handbook/Introduction to Databases/Database Design: Difference between revisions
m (add fromatting) |
m (add prevnext) |
||
| Line 1: | Line 1: | ||
<languages/> | |||
==Database Design== | <translate> | ||
===Database Design=== | |||
Database design needs careful planning. Note that '''''Contacts''''' table redesign proposed in section 1.2 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. | Database design needs careful planning. Note that '''''Contacts''''' table redesign proposed in section 1.2 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. | 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. | ||
{{Prevnext2 | |||
|prevpage=Special:MyLanguage/Kexi/Handbook/Introduction_to_Databases/Database_and_Spreadsheet | |||
|prevtext=Database and Spreadsheet | |||
|nextpage=Special:MyLanguage/Kexi/Handbook/Introduction_to_Databases/Who_Needs_a_Database%3F | |||
|nexttext=Who Needs a Database? | |||
|index=Special:MyLanguage/Kexi/Handbook|indextext=Back to menu | |||
}} | |||
[[Category:Kexi]] | |||
[[Category:Tutorials]] | |||
</translate> | |||
Revision as of 12:52, 20 October 2011
Database Design
Database design needs careful planning. Note that Contacts table redesign proposed in section 1.2 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.