diesel-rs/diesel

More verbose errors on diesel migrations?

Open

#2378 opened on Apr 24, 2020

View on GitHub
 (3 comments) (13 reactions) (0 assignees)Rust (12,054 stars) (1,003 forks)batch import
clienhancementhelp wanted

Description

Right now the error messages aren't very verbose with PostgreSQL when a migration fails, e.g.:

Failed with: syntax error at or near "."

It would be helpful to also display line/column position of the error in the file.

Contributor guide

Tech stack
rustpostgresql
Domain
database
Issue type
feature
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rustdiesel ORMPostgreSQL error reporting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Investigate how diesel currently handles migration errors, particularly the part where raw PostgreSQL error messages are displayed. Look at the `diesel migrations` crate and the `run migrations` function to understand the error flow. Consider using `PQresultErrorField` with `PG DIAG STATEMENT POSITION` to retrieve the line/column number from the server. Check existing comments for any suggested approaches or maintainer hints about acceptable implementation.