Skip to content

Handle config decoding errors from DB charset issues #333

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

jrauh01
Copy link
Contributor

@jrauh01 jrauh01 commented Apr 30, 2025

If the database's character set is not set correctly, the decoding of the config attributes may fail. For that case an error message will be rendered in the form. There will also be a docs entry to prevent that.

Closes #271

@jrauh01 jrauh01 self-assigned this Apr 30, 2025
@cla-bot cla-bot bot added the cla/signed CLA is signed by all contributors of a PR label Apr 30, 2025
@jrauh01 jrauh01 force-pushed the docs/database-encoding branch from e9c817c to 7dbe4bd Compare April 30, 2025 13:42
Render an error message in the form if the config attributes for
the type could not be decoded.
@jrauh01 jrauh01 force-pushed the docs/database-encoding branch from 7dbe4bd to 832c8fb Compare April 30, 2025 13:44
@jrauh01 jrauh01 requested a review from nilmerg April 30, 2025 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla/signed CLA is signed by all contributors of a PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Missing information in docs: Database ressource Character Set needs to be utf8
1 participant