"'rawunicodeescape' codec can't decode bytes in position 24-25: truncated \UXXXXXXXX escape" is displayed if user create table which contains multiple \ with SQL_ASCII encoding.

• OS: [e.g. Windows]
• Mode: [e.g Desktop]

Steps to reproduce the behaviour:

1. create the following database:

CREATE DATABASE a_sql_asscci
WITH
OWNER = postgres
TEMPLATE = template0
ENCODING = 'SQL_ASCII'
CONNECTION LIMIT = -1
IS_TEMPLATE = False;
2. create the following table in a_sql_asscci:
CREATE TABLE public."C:\User\te"
(
"C:\User\te" "char" NOT NULL,
PRIMARY KEY ("C:\User\te")
);

ALTER TABLE IF EXISTS public."C:\User\te"
OWNER to postgres;
3. Table created
4. Click on the newly created table and view data
5. Error "'rawunicodeescape' codec can't decode bytes in position 24-25: truncated \UXXXXXXXX escape" is displayed

Expected behavior

View data should be working if user create table which contains multiple \ with SQL_ASCII encoding.

Reproduce the issue by creating the SQL_ASCII database and table named with multiple backslashes, then use the table's View Data action. Trace the error from that entry point and verify that the table data can be viewed without the rawunicodeescape decoding error.