Re: Data Constraints Vs Application Constraints

From: Kenneth Downs <knode.wants.this_at_see.sigblock>
Date: Wed, 09 Mar 2005 13:26:40 -0500
Message-ID: <for3g2-4ra.ln1@pluto.downsfam.net>

Alfredo Novoa wrote:

> On Wed, 09 Mar 2005 08:37:16 -0500, Kenneth Downs
> <knode.wants.this_at_see.sigblock> wrote:
>

>>Do you know why they did it that way?

>
> The most probable reason is: incompetence.
>

>>  There was definitely a reason and you
>>don't want to ruffle feathers by criticizing it before you know why it was
>>done.  The normal argument is for portability,

>
> No. The normal reason is incompentence. Portability is a poor excuse.
>

>> if they code things in the
>>client, their app will run against many databases.  According to you this
>>worked, so I would ask why change it?  Technically it may be "wrong" but
>>technically they somehow got it working and are a big company, so they
>>must be doing something right?

>
> No, that does not mean that they are doing things right.
>

>>The other hidden reason may be that they did/do not know much about
>>databases, and you want to tiptoe-tiptoe around that one.

>
> That's incompetence :)

Sparky,

You can also take Alfredo's approach. Try calling them incompetent to their face 5-10 times in a 5 minute conversation and let us know how that works out :)

-- 
Kenneth Downs
Secure Data Software, Inc.
(Ken)nneth@(Sec)ure(Dat)a(.com)

Received on Wed Mar 09 2005 - 12:26:40 CST