| Re: Bad database design can cause unnecessary coding [message #179512 is a reply to message #179505] |
Sat, 03 November 2012 14:54   |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma:
|
Senior Member |
|
|
On 11/3/2012 5:17 AM, Tony Marston wrote:
> "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.
>
I can answer sensible questions in an intelligent manner. I can also
recognize spammers when I see them - and I don't support them.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]