Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kXhpD-0005GY-IY for pgadmin-hackers@arkaria.postgresql.org; Wed, 28 Oct 2020 09:32:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kXhpC-00033F-3R for pgadmin-hackers@arkaria.postgresql.org; Wed, 28 Oct 2020 09:32:58 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kXhpB-000338-U0 for pgadmin-hackers@lists.postgresql.org; Wed, 28 Oct 2020 09:32:57 +0000 Received: from mail-lf1-x12c.google.com ([2a00:1450:4864:20::12c]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kXhp9-00026m-Ct for pgadmin-hackers@postgresql.org; Wed, 28 Oct 2020 09:32:56 +0000 Received: by mail-lf1-x12c.google.com with SMTP id l2so6380853lfk.0 for ; Wed, 28 Oct 2020 02:32:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=irLKCwJF6HIYzi21xMaOjjiDC067CEZdsxJjqPzVhrg=; b=SyhxKt7e2gY9DG5B9MSaqf/HONUOIaDCvo06czX+QPVH0lVihovtdiWJl5jB7sz+db VghnCp1FANrRkchXkMqMR93QhcWmRWcGDrOcgaUITR/Fi2i4Q3BI6gqyaHeC0pHiAZSR OvAr8AtuSfJwkHAHFCMnUQPXrbiLcKLxUzvUbnApaCJpWDUL5B1OXox6r6esRXn7kQY2 kTOR5GK68ZGKTcC3b+bVRFjAZKVFGOmwfjl1MDvnQJsJC2rgo9xClQ6AMNqbaHBjWhtY mgs1OTc0bb/hPvgRz30aDapYrpJJ+XwGljpKjbgetHeaAuyUqCteinlh32JTaCuQpsPj HysA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=irLKCwJF6HIYzi21xMaOjjiDC067CEZdsxJjqPzVhrg=; b=bPq0wsRSg5RXRKm3r3r43PHVUAPZTQPtRb/ipo0C3PKMPkEJgyOs8A3Fk9adtCINme 3akUdtCxHU0rOhsoVYd0tFJSacuXeMvzNNUbFyl8qsvdLgsKdnMWA4mzsfYfFkQnWoW5 3j2s/+gy7C+gI1XTDxudN/ROCRleWJUT0GmYcoL8izf9FCHGKvb4sqjMW1dF/dyyEbFo GDqJDd/5wuX0Ijt427rvlA4mvWoGe27p71scFzJbhGF9OTkYc3azEWy07k01xVoMCFKx 04CZ49ppEy7xO4M5SMSqFwJqFTR9XYU5ASeB9/b9C77hJblQGIWOHj0b9TsYBizm0kL7 ATTA== X-Gm-Message-State: AOAM533LvkuOepwNyyp4ojWt11W32HA9bhDjc86qdLCwgT0iSbbX7unv fX+RtmYC5/pJfM049vqp5cp21VQs5KqZpa2f5tBu8cWgzVt0Zc/pQCL28bj+cwq0yqk4zlvliYY OfFRGIDy9eRi0x2sGAhzlE07qAou/+FIfhvrcegWjH87JxeDh9YX/pUkYTV08VPJ8N8Wbda+C3p 6D6pb+52/X1NN4S+/P0feNTA7itYyWZeVhw94IZ49pTbhFhlLvM855EmqMew== X-Google-Smtp-Source: ABdhPJwMALjusB0PKjkOyR4Ulubv8E/+eY8GEO89cY0KvGNY6LNxecbr2U+WnT2yFZZmBHlzaVcZlLxgMoKA1NQ4JhE= X-Received: by 2002:a19:7e8a:: with SMTP id z132mr2193545lfc.8.1603877573317; Wed, 28 Oct 2020 02:32:53 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Khushboo Vashi Date: Wed, 28 Oct 2020 15:02:48 +0530 Message-ID: Subject: Re: [pgAdmin][RM4061]: Backslashes are not handled correctly for SQL_ASCII database in View/Edit table data To: Pradip Parkale Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="0000000000000570b605b2b7d9be" X-CLOUD-SEC-AV-Info: enterprisedb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000000570b605b2b7d9be Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Pradip, With this patch, 4061 is getting fixed but if you enter "za=C5=BC=C3=B3=C5= =82=C4=87", then it is getting displayed as "za=C5=BC\xf3=C5=82=C4=87". So, the fix is not prop= er. Also, if you want to change the typecast, then change the dict which is mapped for Postgres, Python and Typecast encoding in encoding.py file. Thanks, Khushboo On Tue, Oct 27, 2020 at 3:26 PM Pradip Parkale < pradip.parkale@enterprisedb.com> wrote: > Hi Hackers, > > Please find the attached for RM4061. Backslashes were not handled > correctly for SQL_ASCII database. > > > -- > Thanks & Regards, > Pradip Parkale > Software Engineer | EnterpriseDB Corporation > --0000000000000570b605b2b7d9be Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Pradip,

With this patch, 4061 is get= ting fixed but if you enter "za=C5=BC=C3=B3=C5=82=C4=87", then it = is getting displayed as "za=C5=BC\xf3=C5=82=C4=87". So, th= e fix is not proper.

Also, if you want to change t= he typecast, then change the dict which is mapped for Postgres, Python and = Typecast encoding in encoding.py file.

Thanks,
Khushboo



On Tue, Oct 27, 2020 at = 3:26 PM Pradip Parkale <pradip.parkale@enterprisedb.com> wrote:
Hi Hack= ers,

Please find the attached for RM4061. Backslashes we= re not handled correctly=C2=A0for SQL_ASCII database.


--
Thanks & Regards,
Pradip Parkale
Software Engineer | EnterpriseDB Corporation
--0000000000000570b605b2b7d9be--