Environment

• psqldef version: 3.1.10 (4bc218c)
• PostgreSQL version: 15

Issue

I'm experiencing an issue where CREATE TYPE statements work fine with a single table but fail when there are multiple tables in the schema.

Single table (works)

CREATE TYPE order_status AS ENUM ('pending', 'shipped');

CREATE TABLE orders (
    id SERIAL PRIMARY KEY,
    status order_status NOT NULL
);

This applies successfully.

Multiple tables (fails)

CREATE TYPE order_status AS ENUM ('pending', 'shipped');

CREATE TABLE customers (
    id SERIAL PRIMARY KEY
);

CREATE TABLE orders (
    id SERIAL PRIMARY KEY,
    status order_status NOT NULL
);

This fails with ERROR: type "order_status" does not exist.

Observation

When I run with --dry-run, the generated DDL shows different ordering:

$ cat schema.sql
CREATE TYPE order_status AS ENUM ('pending', 'shipped');

CREATE TABLE customers (
    id SERIAL PRIMARY KEY
);

CREATE TABLE orders (
    id SERIAL PRIMARY KEY,
    status order_status NOT NULL
);
$ psqldef --dry-run xxx < schema.sql
BEGIN;
CREATE TABLE customers (
    id SERIAL PRIMARY KEY
);
CREATE TABLE orders (
    id SERIAL PRIMARY KEY,
    status order_status NOT NULL
);
CREATE TYPE order_status AS ENUM ('pending', 'shipped');
COMMIT;

This ordering difference might be causing the issue.

Current Workaround

I'm using --before-apply with idempotent type creation:

-- before.sql
DO $$
BEGIN
    IF NOT EXISTS (SELECT 1 FROM pg_type WHERE typname = 'order_status') THEN
        CREATE TYPE order_status AS ENUM ('pending', 'shipped');
    END IF;
END $$;

psqldef --before-apply="$(cat before.sql)" database < schema.sql

This works, but I'm wondering if there's a better approach or if this is expected behavior?