Hi :) Relational databases have been around for quite a long time now. When many records/rows contain the same data it helps if that data can be held separately so that only 1 instance is held with the many rows simply referencing that 1 instance. That 1 instance can then be edited or updated affecting all the rows/records simultaneously without any worry that some records might not have received the change. It keeps data consistent. It reduces the amount of storage space the database takes up.
Of course, like almost any tool, it can be taken to a ridiculous extreme of diminishing returns where it becomes worthwhile considering alternatives but generally it is a good way of making a database more efficient. Regards from Tom :) On 16 May 2014 07:17, frofa <[email protected]> wrote: > What is the reason you need to split your data into multiple tables? > > You will make life a lot easier for yourself if you are able to consolidate > your data into one table. The rules of data 'normalization' (see link > below) > may require your data to be divided into more than a single table, but this > does not seem like the reason why your data is divided as you describe. > > http://databases.about.com/od/specificproducts/a/normalization.htm > > > -- > To unsubscribe e-mail to: [email protected] > Problems? > http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ > Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette > List archive: http://listarchives.libreoffice.org/global/users/ > All messages sent to this list will be publicly archived and cannot be > deleted > > -- To unsubscribe e-mail to: [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
