Re: Interesting question and debate on ddl tables with datefieldsthatwill not always have a value

Thanks for the response.

Yes, retrofitting a vendor supplied application is not in my list of fun
things. It would be nice if they took that into consideration and did it
though. Would really help with data migrations and add on's like EDI,
shop floor feeds, and so on.

<snip>
I would not, however, retrofit referential integrity onto databases that
already have logic built into the applicatio - *unless* there was a
compelling business reason to rewrite the application. Which, by the
way, might well be the case in a situation where you are converting a
traditional green screen application to a service-oriented architecture.
</snip>
Yes, at that time you have to start considering if you put the RI into the
database, rewrite the existing application to stored procedures for data
access and update, or duplicate the code from the existing application
into the SOA. I'd lean towards putting the RI into the database because
as much as we'd like to think that we can not only lead the horse to water
but make him drink also, some developers will directly access the data and
forgo the stored procedure approach. Doesn't exclude using the stored
procedure approach. Perhaps it might approach a belts and suspenders
mentality.



Rob Berendt