>From: Adriano dos Santos Fernandes >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.
I agree, perhaps it could be made "deprecated" to hold the same value (computed column) as the new "child object field" when the object is a table or view? With regards, Martijn Tonies Upscene Productions http://www.upscene.com Download Database Workbench for Oracle, MS SQL Server, Sybase SQL Anywhere, MySQL, InterBase, NexusDB and Firebird! ------------------------------------------------------------------------------ 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
