Subject | Re: how to delete database object with bogus dependencies |
---|---|
Author | unclejung |
Post date | 2007-08-10T23:43Z |
Never mind. The dependencies weren't bogus. My sql tool didn't know
how to pull system info on computed columns in a view, so it claimed
no dependency. My second query of table RDB$FIELDS and
RDB$RELATION_FIELDS returned the dependent view and I was able to sort
everything out from there.
how to pull system info on computed columns in a view, so it claimed
no dependency. My second query of table RDB$FIELDS and
RDB$RELATION_FIELDS returned the dependent view and I was able to sort
everything out from there.
--- In firebird-support@yahoogroups.com, "unclejung" <jungv@...> wrote:
>
> I have a udf that I can't delete because the database thinks that
> there are dependencies. My sql client didn't think so (SQL Manager
> 2005). I queried the rdb$dependencies table and found 3 dependents
> with value for the fields:
>
> RDB$DEPENDENT_NAME RDB$DEPENDED_ON_NAME RDB$FIELD_NAME
> RDB$DEPENDENT_TYPE RDB$DEPENDED_ON_TYPE
> RDB$126 UDF_GET_LITERAL_VALUE 3 15
> RDB$128 UDF_GET_LITERAL_VALUE 3 15
> RDB$127 UDF_GET_LITERAL_VALUE 3 15
>
> Type 3 is supposed to be a computed column, but I can't find rdb$126,
> rdb$127, and rdb$128 any where in table rdb$fields.
>
> Is it safe to delete these 3 records in the rdb$dependencies as I
> think they are orphans?
>
> Thanks,
>
> - Jung
>