| Re: Bad database design can cause unnecessary coding [message #179516 is a reply to message #179504] |
Sat, 03 November 2012 17:01   |
M. Strobel
Messages: 386
Registered: December 2011
Karma:
|
Senior Member |
|
|
Am 03.11.2012 10:14, schrieb Tony Marston:
> "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
Okay, leave out the nitpicking and take it as constructive proposal.
> 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
Sounds like a lot of work. Advice is okay, work must be payed.
> limited experience not go as far as designing the databases that your applications
> use? Or don't you write database applications?
>
Sorry, I forgot all since I managed DB2 in the early nineties. Forgot all from 15
years as IT trainer. Forgot more than others ever knew :-)
/Str.
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]