From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Dinesh Kumar <dinesh(dot)kumar(at)enterprisedb(dot)com> |
Cc: | Jakub Trmota <jakub(at)trmota(dot)cz>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: pgAdmin bug - SQL creation for foreign keys |
Date: | 2013-07-16 07:23:56 |
Message-ID: | CA+OCxoyF+d1azF4THYb9oKqqC_9B558i7nuqtfa+-F_hZ_ZBzw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi
On Mon, Jul 15, 2013 at 6:55 PM, Dinesh Kumar <dinesh(dot)kumar(at)enterprisedb(dot)com
> wrote:
> Hi Dave,
>
> I am able to re-produce the reported issue and with the create new role
> dialogue box. Please find the attached patch for these reported cases.
>
This fix seems reasonable if we want the keywords to be translated in the
UI, but I don't think we do, because they are keywords not natural
language. Can we just prevent them being translated in the first place? If
they're in the XRC file, that may require us to reset the labels to
un-translated strings in code.
Thanks.
>
> Thanks in advance.
>
>
> Dinesh
>
> --
> *Dinesh Kumar*
> Software Engineer
>
> Ph: +918087463317
> Skype ID: dinesh.kumar432
> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
> *
> Follow us on Twitter*
> @EnterpriseDB
>
> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community> and
> more <http://www.enterprisedb.com/resources-community>
>
>
> On Thu, Jul 11, 2013 at 4:59 PM, Dinesh Kumar <
> dinesh(dot)kumar(at)enterprisedb(dot)com> wrote:
>
>>
>> On Thu, Jul 11, 2013 at 4:55 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>>
>>> Dinesh, can you investigate this please?
>>>
>>>
>> Sure Dave.
>>
>>
>>
>>> On Thu, Jul 11, 2013 at 11:42 AM, Jakub Trmota <jakub(at)trmota(dot)cz> wrote:
>>> > Hello,
>>> > I found bug in pgAdmin III 1.16.1 on Windows 7 (x64). When I use czech
>>> > interface and want to add foreign key, this buggy SQL is generated:
>>> >
>>> > ALTER TABLE app_cache_journal
>>> > ADD FOREIGN KEY (entry) REFERENCES acl_object_parents (object_id) ON
>>> > UPDATE ochránit (RESTRICT) ON DELETE kaskádová akce (CASCADE);
>>> >
>>> > Correct SQL is:
>>> >
>>> > ALTER TABLE app_cache_journal
>>> > ADD FOREIGN KEY (entry) REFERENCES acl_object_parents (object_id) ON
>>> > UPDATE RESTRICT ON DELETE CASCADE;
>>> >
>>> >
>>> >
>>> > --
>>> > 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
>>>
>>>
>> Thanks.
>>
>> Dinesh
>>
>> --
>> *Dinesh Kumar*
>> Software Engineer
>>
>> Ph: +918087463317
>> Skype ID: dinesh.kumar432
>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>> *
>> Follow us on Twitter*
>> @EnterpriseDB
>>
>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community> and
>> more <http://www.enterprisedb.com/resources-community>
>>
>>
>>
>
>
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Dinesh Kumar | 2013-07-16 07:35:08 | Re: pgAdmin bug - SQL creation for foreign keys |
Previous Message | Dave Page | 2013-07-16 07:20:24 | Re: Updated options-query_tool.rst file |