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
I actually haven't tested the anonymization on JSON based fields. I need to do some further investigations with a test setup first.
The error itself is thrown when the anonymizer writes the content of a table into a binary CSV stream and then copies the data into a temporary table, using psycopg2's cursor.copy_from method. Maybe the JSON syntax breaks the streamed data.
Hi, I am sorry I didn't had the time to fix this yet. Mainly because we could not use the pganonymizer for our production databases yet. Currently our PostgreSQL versions don't support JSON columns natively, but I will try to get a closer look into that issue.
Otherwise if you have the time and idea to fix it I appreciate a contribution any time.
I have a strange error:
YAML file:
ui_settings column values:
{"firstTime": true, "licenseBannerHasBeenShown": true}
{"firstTime": true}
{}
What am I doing wrong?
The text was updated successfully, but these errors were encountered: