Hi, At September 3, 2015, 3:22 PM, Claudio Valderrama C. wrote:
> Hello, maybe we can stop this before FB3 is released: > create database 'based.fdb'; > create table t1(a int); > /* RDB$1 is created */ > create table t2(a RDB$1); > show table t2; > A INTEGER Nullable I think this should not be permitted. Because of the problem that you outlined below. Or, if it is to still permit it, Firebird should be able to determine if the implicit domain is used by more than one field, and if yes, then a new implicit domain should be created for the alter type. > Now two fields point to an implicit domain. > alter table t2 alter a type double precision; > show table t2; > A DOUBLE PRECISION Nullable > So far so good, but: > show table t1; > A DOUBLE PRECISION Nullable > We have a problem of quantum entanglement between fields from different > tables. > :-) -- Best regards, Daniel Rail Senior Software Developer ACCRA Solutions Inc. (www.accra.ca) ACCRA Med Software Inc. (www.filopto.com) ------------------------------------------------------------------------------ Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
