From: <no...@so...> - 2001-08-13 05:31:48
|
Bugs item #448062, was opened at 2001-08-04 19:50 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=109028&aid=448062&group_id=9028 Category: Core Engine >Group: Feature - Fixed v1.0 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Claudio Valderrama C. (robocop) Assigned to: Claudio Valderrama C. (robocop) Summary: ALTER DOMAIN leaves CONSTRAINT word Initial Comment: On behalf of Jason Wharton: I noticed that if you alter domain drop constraint and then do this: alter domain .... add constraint check ... that the token constraint gets added into the blob containing the check text. It is possible to do this alter domain .... add check ... and thereby omitting the constraint token altogether. Seems odd to me. CVC: Usually, rdb$fields.rdb$validation_source stores things like CHECK (...) but with the ALTER DOMAIN syntax to include a constraint, if you include the optional CONSTRAINT token, you get in rdb$validation_source CONSTRAINT CHECK (...) this makes DDL extraction harder. It's inconsistent, so I consider it a bug. Also, it's pointless since you can't name the only possible constraint for a domain. C. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=109028&aid=448062&group_id=9028 |