Kexi/Handbook/Introduction to Databases/Database Design: Difference between revisions

From KDE Wiki Sandbox
mNo edit summary
(Marked this version for translation)
Line 1: Line 1:
<languages/>
<languages/>
<translate>
<translate>
===Database Design===
===Database Design=== <!--T:1-->


<!--T:2-->
Database design needs careful planning. Note that '''''Contacts''''' table redesign proposed in section [[Special:MyLanguage/Kexi/Handbook/Introduction_to_Databases/Database_and_Spreadsheet#Data_integrity_and_validity|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.
Database design needs careful planning. Note that '''''Contacts''''' table redesign proposed in section [[Special:MyLanguage/Kexi/Handbook/Introduction_to_Databases/Database_and_Spreadsheet#Data_integrity_and_validity|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.


<!--T:3-->
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.


<!--T:4-->
{{Prevnext2
{{Prevnext2
|prevpage=Special:MyLanguage/Kexi/Handbook/Introduction_to_Databases/Database_and_Spreadsheet
|prevpage=Special:MyLanguage/Kexi/Handbook/Introduction_to_Databases/Database_and_Spreadsheet
Line 15: Line 18:
}}
}}


<!--T:5-->
[[Category:Kexi]]
[[Category:Kexi]]
[[Category:Tutorials]]
[[Category:Tutorials]]
</translate>
</translate>

Revision as of 19:47, 14 December 2011

Other languages:

Database Design

Database design needs careful planning. Note that Contacts 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.