On 09/10/2014 10:34, Martijn Tonies (Upscene Productions) wrote: > You could use FIELD_NAME, for backwards compatibility, but also add a > "child object type" column, for the package extension to distinguish between > functions/procedures/future items.
Use a field with a name for another thing is also not good. > Mind you, a computed field has a different object type number of as well, > compared to a normal field (3 vs 9). Suddenly, rdb$dependent_name holds > the field name, not the table name. > To check for dependencies on these, I have to run a separate query already. RDB$DEPENDENT_TYPE is not important here for packages, and it can surprise you even more. Dependency for (RDB$DEPENDENT_ON_TYPE) computed or not fields are registered consistently. Adriano ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
