[FEATURE]: `CREATE TRIGGER` functions

[MatanYadaev]

trafficstars

Describe what you want

Expected behavior:

export const users = pgTable('users', {
  updatedAt: timestamp('updated_at')
    .defaultNow()
    .notNull()
    // Feature request:
    .triggerBeforeUpdate('set_updated_at', sql`set_updated_at()`),
});

-- Inserted manually in a previous migration file
CREATE OR REPLACE FUNCTION set_updated_at()
    RETURNS TRIGGER AS
$$
BEGIN
    NEW.updated_at = NOW();
    RETURN NEW;
END;
$$ LANGUAGE 'plpgsql';

CREATE TABLE IF NOT EXISTS "users" (
  "updated_at" timestamp DEFAULT now() NOT NULL,
);

CREATE TRIGGER set_updated_at
BEFORE UPDATE ON "users"
FOR EACH ROW
EXECUTE PROCEDURE set_updated_at();

[mattaiod]

It seems to be a priority ! Indeed, it's a very important feature

strength to you and thank you :)

[ItayTamary]

is there an update on the timeline/prioritization for arbitrarily defining triggers within the schema?

strength to you and thank you :)

[ghyath5]

any updates here ?

[Khosraw]

Bump

[mianala]

+1

[Raveen2001]

+1

[adfdev]

+1

[sh-k-l]

+1

[1mono2]

+1

[millette]

@1mono2 @dudubernardino @sh-k-l @adfdev @Raveen2001 @mianala @Khosraw @ghyath5 Your messages are counterproductive. If you're interested and want to share the sentiment, add a reaction to this comment: https://github.com/drizzle-team/drizzle-orm/issues/843#issuecomment-1885771513

That said, I'm also sorry for contributing to the noise since everyone here will get a notification for my comment.

[zackwalton]

Bump