You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: