Subject | Re: [IB-Architect] Table Inheritance |
---|---|
Author | Tim Uckun |
Post date | 2000-07-17T21:14:44Z |
At 04:08 PM 07/17/2000 -0400, you wrote:
Encapsulating the column and trigger definitions into a single
:wq
Tim Uckun
Due Diligence Inc. http://www.diligence.com/ Americas Background
Investigation Expert.
If your company isn't doing background checks, maybe you haven't considered
the risks of a bad hire.
> >you are writing the same trigger over and over again is not because theYou would know much better then I.
> >tables are almost the same it's because they contain the same field.
> >
>
>That actually is substantially more difficult to implement than either
>of the table inheritance models for a variety of reasons:
Encapsulating the column and trigger definitions into a single
>mechanism has a nice piece of elegance, you much admit.Yes indeed. It seems like a elegant way to solve the problems.
:wq
Tim Uckun
Due Diligence Inc. http://www.diligence.com/ Americas Background
Investigation Expert.
If your company isn't doing background checks, maybe you haven't considered
the risks of a bad hire.