> relationships? I would never handle anything in code that
> could be done with the native functionality of the DBMS.
I haven't seen any suggested solution that could handle this problem with
relationships alone. (Note: triggers aren't relationships.) Remember, the
problem is the need to be able to make a blanket statement that covers not
only current entities within the database, but ones that don't exist yet.
As for not handling anything in code that you could do with native DBMS
functionality, it's worth pointing out that you could put almost every bit
of your application logic within stored procedures, but that doesn't mean
you should.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
