Обсуждение: Error "Column not found in pgSet: size" in pgAdmin 1.12
when selects indexes node in object browser error appears (see screenshot) Postgresql server version postgresql-8.4.4 -- All bugs reserved
Вложения
On Fri, Sep 17, 2010 at 10:10 AM, Timon <timosha@gmail.com> wrote: > when selects indexes node in object browser error appears (see screenshot) > Postgresql server version postgresql-8.4.4 I think this is caused by translation of a string that shouldn't be translated. Can you try the attached patch please? -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise Postgres Company
Вложения
On Fri, Sep 17, 2010 at 11:36 AM, Timon <timosha@gmail.com> wrote: > 2010/9/17 Dave Page <dpage@pgadmin.org>: >> On Fri, Sep 17, 2010 at 10:10 AM, Timon <timosha@gmail.com> wrote: >>> when selects indexes node in object browser error appears (see screenshot) >>> Postgresql server version postgresql-8.4.4 >> >> I think this is caused by translation of a string that shouldn't be >> translated. Can you try the attached patch please? > It seems to be true, because in EN_en every thing is fine. > With patch works fine. > Should I fix translation? Or is there any words list that translator > shouldn't translate? No, the patch is the correct fix. Thanks for testing. Unfortunately though, this will not make it into 1.12.0, but I'll commit for 1.12.1. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise Postgres Company
please don't forget to add this patch in pgAdmin 1.12.1 :) 2010/9/17 Dave Page <dpage@pgadmin.org>: > On Fri, Sep 17, 2010 at 11:36 AM, Timon <timosha@gmail.com> wrote: >> 2010/9/17 Dave Page <dpage@pgadmin.org>: >>> On Fri, Sep 17, 2010 at 10:10 AM, Timon <timosha@gmail.com> wrote: >>>> when selects indexes node in object browser error appears (see screenshot) >>>> Postgresql server version postgresql-8.4.4 >>> >>> I think this is caused by translation of a string that shouldn't be >>> translated. Can you try the attached patch please? >> It seems to be true, because in EN_en every thing is fine. >> With patch works fine. >> Should I fix translation? Or is there any words list that translator >> shouldn't translate? > > No, the patch is the correct fix. Thanks for testing. > > Unfortunately though, this will not make it into 1.12.0, but I'll > commit for 1.12.1. > > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise Postgres Company > -- All bugs reserved
On Tue, Sep 28, 2010 at 1:50 PM, Timon <timosha@gmail.com> wrote: > please don't forget to add this patch in pgAdmin 1.12.1 :) Ooops - thanks! -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise Postgres Company