Re: pgAdmin3: check_option translated in View editing dialog

Hi Sebastian,

We have just tried to reproduce the issue but not able to understand the
issue from the description.

We followed below steps.

1. Change the language to German.
2. Open the existing View's properties and try to change "With check
option".
3. Open SQL tab - According to change in option, we are able to see and
edit the query.

Let me know if anything missing in above steps or Can you please give steps
to understand the issue ?

Thanks,
Neel Patel

On Wed, Dec 23, 2015 at 7:09 PM, Neel Patel <neel(dot)patel(at)enterprisedb(dot)com>
wrote:

> Hi Dave,
>
> Sure. I will look into this issue.
>
> Thanks,
> Neel Patel
>
> On Wed, Dec 23, 2015 at 7:04 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>
>> Neel, can you look into this please?
>>
>> Thanks.
>>
>> On Wed, Dec 23, 2015 at 1:25 PM, Sebastian Albert
>> <albert(at)math(dot)uni-goettingen(dot)de> wrote:
>> > -----BEGIN PGP SIGNED MESSAGE-----
>> > Hash: SHA256
>> >
>> > Dear pgAdmin-Hackers
>> >
>> > I observed the following minor issue in pgAdmin3 1.20.0
>> > For I did not find a bugtracker, I'm mailing it to the list. Please
>> > point me to it if there is one.
>> >
>> > pgAdmin appears to me translated (into German) in part, probably due
>> > to my locale. However, in the dialog for editing a VIEW's properties,
>> > the generated SQL reads
>> >
>> > ALTER VIEW myview
>> > SET (check_option=nein);
>> >
>> > with "Nein", "Lokal" and "Cascaded" offered in the corresponding
>> > dropdown. I can manually edit these two lines away in the SQL tab of
>> > the dialog, but it's probably not intended that way.
>> >
>> > - -- Sebastian
>> > -----BEGIN PGP SIGNATURE-----
>> > Version: GnuPG v2
>> >
>> > iQIcBAEBCAAGBQJWeqDgAAoJEKZN7hpT3kUKC4gP/jCdUy64KlCmGbFH5vOapyCh
>> > CcicKABS8EtuUpaFEgxPJCemtplSzS9oNzDKBtSKD1MxxoDN/Sjreuw7wYtzmO+/
>> > U/JIA4rGqP1FgVldXqDuaw4Hih76gRW3XOqTzv+kkqmt/G/0JrKlMDyY9QKPgHw9
>> > qB2o5Nf9E4QLWyTZkRJqiCuCARsYvHAUWafOINgPx3fpl2cTinSN7/mT8AaLCtXT
>> > y09MmNvqGp1ILqYp81AsXblPUADdW5rLjcCxD70QIE7ejuej9EtmGYQWLGr8Bo1d
>> > UnUUQNPuYjrfjInj15Odirmw+hUnfu1iIwjUUze6no4o9FwOmLYx0OKw2gw+QG1H
>> > byL+JR3wb6H7sa5RgLeNvW90feP7XFsQsKPUREovVNX891ZxGkdNZEknhaL8TYyj
>> > 8xCqoX9+yecixDA4U9wZIFfsD6b9cNBFRUjOHKLS1qnQ+zQgWQLlUxXAjLiLawgE
>> > AbB9rf6N9HzLIhVlqd7u/HpNOamUgXrdwBAd7DNiyqqsVdxaOzEFT3bXpgv5UQA/
>> > F2eyQi35MCzoROcMoVKUT5kVKKo1UcMkymThWV4s78Lv2C7jM+8GX79gcIpGSps5
>> > mSJLXHLUH03SozfZeGh3DBsl6UyhRHM8GVghCZutHzj68ViM4MSKgPX8RU+wBUxs
>> > 8ZpeXtC927azi9NJcNP6
>> > =yrr2
>> > -----END PGP SIGNATURE-----
>> >
>> >
>> > --
>> > Sent via pgadmin-hackers mailing list (pgadmin-hackers(at)postgresql(dot)org)
>> > To make changes to your subscription:
>> > http://www.postgresql.org/mailpref/pgadmin-hackers
>>
>>
>>
>> --
>> Dave Page
>> Blog: http://pgsnake.blogspot.com
>> Twitter: @pgsnake
>>
>> EnterpriseDB UK: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>>
>
>