Re: What are the consequences of a bad database design

From: "Costin Manda" <siderite(at)madnet(dot)ro>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: What are the consequences of a bad database design
Date: 2005-04-11 10:00:43
Message-ID: 1892.193.226.119.24.1113213643.squirrel@193.226.119.24
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> But the people i am working with are not considering the restructuring of
> the database. They are even thinking of expanding it by adding new
> modules.

> Please can someone advise me, or tell me what to do, what may be the
> consequences

I have been working with databases for web scripts (PHP) and all sorts
of stupid billing systems and databases. Right now my system uses PHP to
access mysql, postgres and mssql databases in the same time. The only
possible solution for many of these problems was to create by own
database with my own tables and create a script to replicate the data
from one to the other periodically.
I think that you should try to move the system to your own way of
thinking and doing things and leave them the alternatives. Sooner or
later they will use your system as it is better.

-------------------------
E-Mail powered by MadNet.
http://www.madnet.ro/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sebastian Hennebrueder 2005-04-11 10:05:37 Asyncron replication from wan to lan with PostgreSQL 8
Previous Message Rafael.Hernamperez 2005-04-11 09:53:27 Re: What are the consequences of a bad database design (never