| Re: Bad database design can cause unnecessary coding [message #179505 is a reply to message #179494] |
Sat, 03 November 2012 09:17   |
Tony Marston
Messages: 57
Registered: November 2010
Karma:
|
Member |
|
|
"Jerry Stuckle" wrote in message news:k708e6$fjt$1(at)dont-email(dot)me...
>
> On 11/2/2012 3:12 AM, Tony Marston wrote:
>> 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? I have been designing
>> databases, and building the applications which use them, for several
>> decades, and I have learned over the years that there are some design
>> decisions which help the developer while others do nothing more than
>> hinder. I have produced a document which lists 14 of these “hindrances”
>> which can be read at
>> http://www.iamaspammer.net/php-mysql/database-design-ru-novice-ninja-or-nin compoop.html
>>
>>
>> Do you agree with my opinions? Can you think of any more questionable
>> design decisions which can be added to this list?
>>
>> Tony Marston
>>
>> http://www.iamaspammer.net
>> http://www.iamaspammer.org
>
> You wouldn't know a good design if it was shown to you, spammer.
>
Hi Jerry,
I thought that you had put me in your kill file long ago, so why are you
still looking at (and responding to) my posts.
I still see that you are incapable of answering a sensible question with an
intelligent answer.
--
Tony Marston
http://www.tonymarston.net
http://www.radicore.org
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]