-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
libgixsql-pgsql error logging defect #84
Labels
bug
Something isn't working
Comments
GitMensch
added a commit
to GitMensch/gixsql
that referenced
this issue
Jul 6, 2022
fixes mridoni#84 (at least its main issue)
Yes, connection errors are not logged properly, I cannot test it right now, but this patch should fix it. |
I came to the same conclusion. |
mridoni
added a commit
that referenced
this issue
Jul 13, 2022
- Added support for "smart" cursor initialization (#88) - Added support for EXECUTE prepared-statement INTO #(87) - Fixed a logging problem (#84) - Fixed "wrong generated COBOL in 1.0.16" (#83) - Fixed "missing "close" for spdlog?" (#82) - Added support for using prepared statements in cursors (#81) - Variable length fields indicators are now 32-bit long by default (#80) - Added support for using variable length fields with prepared statements (#79) - Added upport for using group fields in INSERT and SELECT..INTO statements (#6) - Added support for more connection string formats (including ocesql compatibility) (#16) - Added Support for DISCONNECT ALL (#89) - Performed some refactoring to improve code size - Fixed a few memory leaks
fixed in 1.0.17 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm currently hunting down an error and had a look at the error logging:
... looks like the actual error message from libpg is missing :-(
Note: the trace log is better in all places that are self-generated (it is "just" the error message from libpg that is missing)
... it looks like that "Data source info" may miss some information, too - but I guess that only serves as a "title" to the next line?
Side note: Interestingly the "debug" level has less information than the "trace", I would have thought it to be the other way around.
The text was updated successfully, but these errors were encountered: