| From: | Jose Soares <jose(dot)soares(at)sferacarta(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | database design best pratice help |
| Date: | 2013-01-28 09:45:41 |
| Message-ID: | 510648C5.5040700@sferacarta.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2013-01-28 10:02:21 | Re: database design best pratice help |
| Previous Message | Fredrik.HuitfeldtMadsen | 2013-01-28 09:03:39 | Re: [pgpool-general: 1315] Re: Database connections seemingly hanging |