Subject | Re: [IB-Architect] Identifier naming woes |
---|---|
Author | Ann W. Harrison |
Post date | 2001-05-24T23:19:53Z |
At 04:38 PM 5/24/2001 -0400, David Jencks wrote:
and must be deleted before the field can be dropped. Computed
fields cause the following bizarre error message, but do not
allow the field to be dropped.
QLI> alter table x drop x1;
tatement failed, SQLCODE = -104
Invalid request BLR at offset 11
column X1 is not defined in table X
Regards,
Ann
www.ibphoenix.com
We have answers.
>Are you proposing immutable ids and tracking name -- id correspondence?Yes ... and I'm probably wrong.
>Does this mean if you remove a column from a table you can break lots ofViews, triggers, & stored procedures appear to be tracked,
>things that depend on it?
>What specifically?
and must be deleted before the field can be dropped. Computed
fields cause the following bizarre error message, but do not
allow the field to be dropped.
QLI> alter table x drop x1;
tatement failed, SQLCODE = -104
Invalid request BLR at offset 11
column X1 is not defined in table X
>Clearly we need to keep track of all dependencies somehow.Sounds right.
>
>choices are:
>
>use names, and if name changes update all dependent info,
Regards,
Ann
www.ibphoenix.com
We have answers.