On Saturday, September 8, 2018, PG Doc comments form <nore...@postgresql.org> wrote:
> the constraints shown in the table > definition do not apply to values of the composite type outside the table. > (A partial workaround is to use domain types as members of composite > types.) > > The part: > >(A partial workaround is to use domain types as members of composite > types.) > > From here I can understand that workaround is possible. > > But what is workaround? and why it is partial? > Would be great to have this description. > The main thing is that some constraints are implemented via triggers and those can only be attached to actual tables. So in the example the REFERENCES constraint can only be used on the original table records and can never applied to a standalone value of that type. David J.
