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.
On Thu, Jul 11, 2013 at 4:55 PM, Dave Page <dpage@pgadmin.org> wrote:
Dinesh, can you investigate this please?
Sure Dave.
On Thu, Jul 11, 2013 at 11:42 AM, Jakub Trmota <jakub@trmota.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@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgadmin-hackers