Re: Database Design Best Practice help
- From: Timo Raitalaakso <rafu@xxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Mon, 28 Jan 2013 11:16:31 +0200
Hi,
I would suggest going to another direction. Are those code columns
primary keys to the tables? Hopefully you have foreign keys in your
schema. Going to more general way you loose information that comes from
the relationships . The schema should tell the user something about the
data inside. Change the code column names to be more informative names
like productcode and countrycode.
--
Timo Raitalaakso
http://rafudb.blogspot.com/
On 28.1.2013 11:03, Jose Soares wrote:
> Hi all,
>
> I have a question about database design best pratice.
>
> In my db I have about one hundred tables like this:
>
> code
> description
>
> To avoid to have a so great number of similar tables in the db
> I wonder if it is a good idea to unify all these tables in one big table
> like this:
>
> id
> code
> table_ name
> description
>
> The advantages are:
>
> 1. only one table in the db instead of 100
> 2. only one controller to manage the table
>
> Could this be a way to enhance db performance?
> Is there any negative point that I don't see?
>
> Thanks for any comments.
>
> j
>
>
>
>
>
>
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
