| From: | Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com> |
|---|---|
| To: | tutiluren(at)tutanota(dot)com |
| Cc: | Pgadmin Support <pgadmin-support(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Incredibly obvious bug found. |
| Date: | 2019-10-14 04:38:12 |
| Message-ID: | CAFOhELc5OZ5+3LMxHztGNS8VWAnAGBLCNLDyXKNwf6TOF8yriA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
Hi,
On Sat, Oct 12, 2019 at 8:56 PM <tutiluren(at)tutanota(dot)com> wrote:
> When trying to make a UNIQUE constraint, pgAdmin 4 got confused and
> couldn't continue just because my field name contained a space. For some
> absurd reason, it doesn't add the quotes around identifiers and thus breaks
> for anyone who doesn't code with 1970s-era, US-centric name conventions. It
> displayed it to me as "stuff%20whatever" when the name was "stuff whatever".
>
> This is working fine for me with the latest pgAdmin 4. Please try with the
latest pgAdmin 4 and if in case you still face the issue, please log the
issue @ https://redmine.postgresql.org/projects/pgadmin4 with the below
details.
1) pgAdmin 4 version and OS details
2) Screen-shots
Thanks,
Khushboo
I was forced to figure out how to do it in raw SQL.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arni Kromić | 2019-10-14 07:21:15 | Re: Restore item in server menu (suggestion) |
| Previous Message | Alex Williams | 2019-10-14 02:55:10 | Is pgadmin4 being developed at Microsoft? |