Re: Data Constraints Vs Application Constraints

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 :)

>So to sum up, leading with the idea that a working app has been done wrong
>is probably a bad idea.

It depends on many things. Specially on how smart and educated the managers are.

But the honest and professional behavior is to say the truth.

I would not like to work in a company that forces to me to lie and to be unprofessional.

Regards Received on Wed Mar 09 2005 - 17:10:03 CET