Commented by: Ain Valtin (ain)

As far as I can see, the domain doesn't have to be used by PK - I do get similar error when trying to alert one which isn't used by any PK / FK (using 2.0.3).

Commented by: Smirnoff Serg (wildsery)

Dependence problem exists for any field domains that is used by (for ex. by proc).
The error is:
"This operation is not defined for system tables.
unsuccessful metadata update.
Column ... from table ... is referenced in ..."

Thinks that if altering domain is proper action, than no need to lookup some additional boundaries like field usage.
If user do this, than he know what to do, and the shooting leg will be on his conscience.

Whether or no, now user skip the proper ALTER command and use the "update rdb$fields" that is quite dangerous but meet no dependencies problems.

Commented by: @dyemanov

Serg, I think you mention a different (although related) issue here. Index is not a regular (usually PSQL) dependency and is likely to imply a separate set of rules.

Commented by: Smirnoff Serg (wildsery)

So what to do? Create separate ticket?

Commented by: Alvaro Castiello (acastiello)

This issue is a most. The whole pourpose of using domains is not have to recreate the database when you need to change one of such domains