Dmitry wrote:
> > Extend the syntax but preserve backward compatibility via default:
> >
> > COMMENT ON [{PROCEDURE | FUNCTION}] PARAMETER ...
>
> but if the object type specifier is omitted, then the engine tries to be
> smart and determine whether it's a procedure or a function at runtime
> (by searching in both tables). In the case both exist with the same
> names, an ambiguity error is thrown.
This would definitely be my preference, rather than creating an arbitrary
difference between a procedure PARAMETER and a function ARGUMENT.
It's analogous to selecting unqualified column names from a JOIN: you can do
it, but if the column exists in more then one participant, an error is thrown.
My 2 cts.
Paul Vinkenoog
------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
