Re: Need SQL Server Temp Table equivalent (challenge!)

On 28 Jul 2003, kin_ng5_at_yahoo.com wrote:

> However, my constraints are not implemented on the DB level but
> on the application level. This mostly is stored procedures.
> Normally I would have the same reactions as you when somebody
> says they want the program to control the verification logic
> instead of the DB. But for the flexibility of our system in
> adopting changes to the business, this is the extreme we have
> taken. Also an assumption of our design was that only IT will
> make most of the relationship changes (via the GUI front end of
> our system). Again, this is a compromise.

Well, I'm happy it works for you. There are many ways to build an app. I just think you probably should have gone with a much more flexible storage-based solution to begin with, maybe an XML based solution or some completely OO based storage? Choosing an RDBMS should immediately say that you want to use relationship modeling as the central tenet to your data storage needs. In choosing an RDBMS, you inherently asked to be hampered when it comes to redesigning your database. You asked for this in the same way one asks that stop lights work correctly, even at the expense of being slowed down on his way to work. The safety on the road is too important, even to the detriment of getting to work more quickly.

I wish you luck in not getting hit while crossing the street.

-- 
Galen Boyer