Re: Database structure
Posted by:
moondog
Date: May 24, 2005 09:28AM
You are right: keeping all the data in one single table eliminates the risk of duplication.
My mistake was not to foresee possible future different uses of the application: right now each shop operates independently one from the other and only names and addresses are collected, no transactions recorded or anything fancy, so I guess that my structure would work anyway but it's not such a good one, as specs may change during development. The
The splitting of data over different tables originated from my concern about having so many records in one table, thinking it may cause problems: are there particular issues I should be aware of, in dealing with such big tables?
Subject
Written By
Posted
Re: Database structure
May 24, 2005 09:28AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.