--- In [email protected], Thomas Steinmaurer <ts@...> wrote: > I see no reason that DEFAULT NULL is part of the parameter list for the > domain, if the underlaying domain has already DEFAULT NULL defined. > > For example: > > CREATE DOMAIN D_INT AS > INTEGER > DEFAULT NULL > ; > CREATE DOMAIN D_INT2 AS > INTEGER > ; > > > I end up with the DDL for a procedure using both domains and explicitly > using DEFAULT NULL for the second in the SP parameter list: > > SET TERM ^^ ; > CREATE PROCEDURE P_1 ( > P1 D_INT, > P2 D_INT2 DEFAULT NULL) AS > BEGIN > SUSPEND; > END ^^
Thanks Thomas for your response. I get your point. I don't have a DEFAULT in the DOMAIN though in which case I might want to use DEFAULT NULL in the SP parameters, but it does not stick for me. Please advise. Regards Bhavbhuti
