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

fix(postgres): don't panic if M or C Notice fields are not UTF-8 #3346

Merged
merged 3 commits into from
Jul 16, 2024

Commits on Jul 13, 2024

  1. fix(postgres): don't panic if M or C Notice fields are not UTF-8

    This has been observed with an old version of PostgreSQL (11.0.4)
    running on Windows Server 2016 with windows-1252 encoding and French
    locale.
    
    This change replaces invalid UTF-8 fields with a default string, so the
    other fields can still be read if they are valid.
    YgorSouza committed Jul 13, 2024
    Configuration menu
    Copy the full SHA
    362ca98 View commit details
    Browse the repository at this point in the history

Commits on Jul 16, 2024

  1. Revert "fix(postgres): don't panic if M or C Notice fields are no…

    …t UTF-8"
    
    This reverts commit 362ca98.
    YgorSouza committed Jul 16, 2024
    Configuration menu
    Copy the full SHA
    6e915f2 View commit details
    Browse the repository at this point in the history
  2. Check that Notice M and C fields are valid UTF-8

    Otherwise, we return the invalid UTF-8 error to avoid panicking later.
    YgorSouza committed Jul 16, 2024
    Configuration menu
    Copy the full SHA
    7aa6ca1 View commit details
    Browse the repository at this point in the history