Re: Composite type: Primary Key and validation

On 6/5/23 08:06, Lorusso Domenico wrote:
> Thank's, you are right, I've the same doubts.
> A composite type is useful because I've to add all these information on
> many tables and because it more easy to pass all these informations to
> functions that have to ensure the right format and evaluation.

I do that with a Sqitch(https://sqitch.org/) template, the relevant part
being:

...

CREATE TABLE [% IF schema %][% schema %][% ELSE %]schema_name[% END
%].[% IF table %][% table %][% ELSE %]table_name[% END %](
     line_id         integer GENERATED ALWAYS AS IDENTITY PRIMARY KEY,

     ts_insert       timestamptz NOT NULL DEFAULT now(),
     ts_update       timestamptz,
     user_insert     varchar(20) NOT NULL DEFAULT "session_user"(),
     user_update     varchar(20)
);

...

I then add the table specific fields after Sqitch creates the deploy
script from the template.

>
> Talking about first point I could use the "table inheritance", but I've
> to reset all constraints for each table :-(
>

> --
> Domenico L.
>
> per stupire mezz'ora basta un libro di storia,
> io cercai di imparare la Treccani a memoria... [F.d.A.]

--
Adrian Klaver
adrian.klaver@aklaver.com