yesodweb/persistent

Postgres migrations should not trigger if the unique key is too long

Open

#1,515 opened on Aug 29, 2023

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Haskell (302 forks)auto 404
Postgresbuggood first issue

Repository metrics

Stars
 (484 stars)
PR merge metrics
 (PR metrics pending)

Description

A table with a long uniqueness key will trigger a migration, but Postgres will silently truncate it to the original length. persistent-postgresql's migrations should truncate the name of a constraint before checking if it needs to be renamed.

Contributor guide

Research direction
Investigate how persistent postgresql handles constraint naming and truncation in migrations.
Tech stack
haskellpostgresql
Domain
database
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitHaskellPostgreSQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45