Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add file name to errors #526

Open
timvandam opened this issue May 27, 2023 · 4 comments
Open

Add file name to errors #526

timvandam opened this issue May 27, 2023 · 4 comments

Comments

@timvandam
Copy link

Is your feature request related to a problem? Please describe.
Pgtyped runs 6 threads in parallel whenever I run it, but this makes it hard to find out in which files errors are happening since they are all being processed in parallel. Adding the file name to errors would be great to prevent this.

When actively making a query this isn't really an issue, but I just changed my schema slightly and had to search through 29 .sql files

Describe the solution you'd like
File name added to error logs

@zacherkkila
Copy link

This would be a fantastic add.. drives me crazy when I have many files and have to hunt down issues after a schema change

@bbsimonbb
Copy link

This is bugging us as well. This would be a big improvement.

@domdinnes
Copy link

Error messages currently look like this:

Error in query. Details: {
  errorCode: 'scanner_yyerror',
  hint: undefined,
  message: 'syntax error at or near "VALUES"',
  position: '124'
}

I'd like to see both the file and query name in the error message. As people above have mentioned - it makes tracking down problems difficult, especially after schema changes.

@cakerug
Copy link

cakerug commented Sep 24, 2024

+1 Would be great to have this fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants