| Re: Bad database design can cause unnecessary coding [message #179504 is a reply to message #179493] |
Sat, 03 November 2012 09:14   |
Tony Marston
Messages: 57
Registered: November 2010
Karma:
|
Member |
|
|
"M. Strobel" wrote in message news:afhg10Ff1jjU1(at)mid(dot)uni-berlin(dot)de...
>
> Am 02.11.2012 08:12, schrieb Tony Marston:
>> When you design your database for your PHP application are you aware that
>> some of
>> your design decisions can have a detrimental effect when it comes to
>> writing the code
>> to access that database?
>
> All your design decisions can have a detrimental or beneficial effect. The
> word "can"
> even is too weak, since the database design is the base of your
> application.
>
> I don't like the phrasing "code to access the database". What you want to
> access AND
> use is your data.
>
> Maybe I am nitpicking, but precision in wording shows precision in concept.
> That is
> what programmers need.
>
> /Str.
Instead of nitpicking over the words I used why don't you try and show how
intelligent you are by commenting on the 14 "bad" practices that I have
identified. Do you agree with them? Do you disagree? Do you have any more to
add? Or does your limited experience not go as far as designing the
databases that your applications use? Or don't you write database
applications?
--
Tony Marston
http://www.tonymarston.net
http://www.radicore.org
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]