rubenv / rubenv/sql-migrate

sql-migrate status fails with "Could not create constraint or index"

Open
#211 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
3.4k
Forks
292
PR merge metrics
No merged PRs in 30d

Description

$ go get -v github.com/rubenv/sql-migrate/...@v1.1.1
$ sql-migrate status -env="dev"
mssql: Could not create constraint or index. See previous errors.

How can I see previous errors as nothing else is output in the terminal. Also why is a constraint or index attempting to be created when running the status command?

Contributor guide

No contributing guide indexed for this repository

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

Reproduce the reported sql-migrate status -env="dev" command using sql-migrate v1.1.1 against MSSQL, then trace the status operation and its error-reporting path. Determine why status attempts to create a constraint or index and ensure the underlying MSSQL error is surfaced; verify the behavior with a focused regression test if the repository provides one.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, sql
Domain
cli, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.