> I am trying to make DEFAULT NULL stick for a couple of SP parameters. I > generally use DOMAIN but when I did it through DOMAIN (and FlameRobin) the > DEFAULT would not make it to the final DDL. When I used FireBird types the > DEFAULT remained. > > The DEFAULT NULL in below got ignored in the final DDL > TCPROMPT CHAR250 DEFAULT NULL, > TCSEP CHAR250 DEFAULT NULL ) > > The DEFAULT NULL makes it through to final DDL > TCPROMPT Char(250) DEFAULT NULL, > TCSEP Char(250) DEFAULT NULL ) > > Please advise
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 ^^ -- With regards, Thomas Steinmaurer Upscene Productions http://www.upscene.com http://blog.upscene.com/thomas/ Download LogManager Series, FB TraceManager today! Continuous Database Monitoring Solutions supporting Firebird, InterBase, Advantage Database, MS SQL Server and NexusDB!
