sqlalchemy / sqlalchemy/alembic

Add support for triggers

Open
#504 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature low priority
Dominant language
Python
Stars
4.4k
Forks
375
PR merge metrics
No merged PRs in 30d

Description

Migrated issue, originally created by Michael Nagel

As far as I can tell it is currently not possible to create and/or manage triggers.
Is this correct? Has there been any discussion on this topic? Are there any plans to add support for this?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by defining the expected scope for creating and managing database triggers across supported migration backends, then identify the relevant migration operations and tests. Done should include an agreed trigger interface, documented behavior, and coverage for the supported cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, sql, sqlalchemy
Domain
database
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.