Re: What are the consequences of a bad database design (never seen

Thanx guys for the advices.

i think i will have to find some "POLITICAL" approach in order to
restructure the existing database, which i am not so good at but worse
trying. Note that even the code is Bad (they are using PHP for a big
application - no object oriented design - a lot of code redundancy ...).

However, it seems difficult to fix the database bit by bit cause as far as i
have seen one or more primary TAble(s) are missing !! So instead of using
an ID, 3-4 fields are being rewritten in almost every table ! So if i have
to build the primary tables, i have to change all the other tables replacing
the combined fields with the corresponding ID ... and there is many others
modifications which could lead to eventuel code modification even if i
change the Views in order to mask the changes. (Thanx god they are using
Views !!!!!)

Anyways it seems i have a major modification that will need time and they
are giving me Time for adding modules not the time for fixing the existing.

So basically what is happening is du to the bad database and code design:
Writing a simple Task is becoming difficult and requires minimum 4 times
more time than in the case of a good design.
So development time is wasted, and data Corrections are being done almost
every day by the stuff here ...

Thanx again.
Jinane.

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.com/