Functions that accept an array of row types are not preserved in the migration

[awgneo]

Hello,

I have this table in Postgres 17 using SQL to define my input file:

CREATE TABLE agreego.relation (
  id uuid NOT NULL,
  "type" agreego.relation_type NOT NULL,
  "constraint" text NOT NULL,
  source_type text NOT NULL,
  source_columns text[] NOT NULL DEFAULT '{}',
  destination_type text NOT NULL,
  destination_columns text[] NOT NULL DEFAULT '{}',
  prefix text NULL,
  CONSTRAINT pk_relation PRIMARY KEY (id),
  CONSTRAINT u_relation UNIQUE (id, "type"),
  CONSTRAINT u_relation_constraint UNIQUE (source_type, destination_type, prefix)
);

And this function:

CREATE OR REPLACE FUNCTION agreego.reduce_entity_relations(
  relations agreego.relation[],
  "relative" JSONB,
  relation_name TEXT
) RETURNS agreego.relation AS $$

It takes an array of the automatically-generated Postgres table row type agreego.relation as relations.

After running atlas migrate diff, the migration file contains this function definition:

-- Create "reduce_entity_relations" function
CREATE FUNCTION "agreego"."reduce_entity_relations" ("relations" "agreego"."relation", "relative" jsonb, "relation_name" text) RETURNS "agreego"."relation" LANGUAGE plpgsql AS $$
DECLARE
  matching_relations agreego.relation[];
  matched_relation agreego.relation;
BEGIN

Notice how relations went from agreego.relation[] to agreego.relation, generating an improper function signature in the database.

Let me know if this is enough information to resolve the issue.

Cheers,
Alex Groleau
(Pro Member)

[awgneo]

A quick update.

Using a composite type instead:

CREATE TYPE agreego.relation_row AS (
  id uuid,
  "type" agreego.relation_type,
  "constraint" text,
  source_type text,
  source_columns text[],
  destination_type text,
  destination_columns text[],
  prefix text
);

With this new function definition:

CREATE OR REPLACE FUNCTION agreego.reduce_entity_relations(
  relations agreego.relation_row[],
  "relative" JSONB,
  relation_name TEXT
) RETURNS agreego.relation_row AS $$

Correctly generates the function signature with []:

-- Create "reduce_entity_relations" function
CREATE FUNCTION "agreego"."reduce_entity_relations" ("relations" "agreego"."relation_row"[], "relative" jsonb, "relation_name" text) RETURNS "agreego"."relation_row" LANGUAGE plpgsql AS $$

So this issue seems specific to the usage of Postgres table row types used as an array in functions. Hopefully Postgres does actually support this.

Cheers,
Alex