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.

Sign up for GitHub

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

Jump to bottom

db-sync: Reject TxMetadata objects containing NUL characters #298

Merged
merged 1 commit into from
Sep 21, 2020
Merged

db-sync: Reject TxMetadata objects containing NUL characters #298

merged 1 commit into from
Sep 21, 2020

Commits on Sep 21, 2020

  1. db-sync: Reject TxMetadata objects containing NUL characters 

    TxMetadata is stored as JSON and that JSON is stored in a 'jsonb' column
in PostgreSQL. However, there are limitations to that Postgres 'jsonb'
data type. Specifically, it cannot contain Uniciode NUL characters. This
temporary fix simply drops TxMetadata JSON objects that would otherwise
be rejected by Postgres. Hopefully a better solution will be will be
dreamt up and implemented later.

Temporary workaround fix for:
#297
    @erikd
    erikd committed Sep 21, 2020
    Configuration menu
    Copy the full SHA
    c7ac532 View commit details
    Browse the repository at this point in the history