We can't do anything about length restrictions in those controls, except suggest the use of the max length option, which will work correctly as of 1.16.2.
On Thu, Aug 8, 2013 at 1:04 PM, Dinesh Kumar <dinesh.ku...@enterprisedb.com>wrote: > Hi Dave, > > Adding to previous e-mail, i have tested this on Windows 7 with the latest > pgAdmin master branch. > > 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> > > > On Thu, Aug 8, 2013 at 5:32 PM, Dinesh Kumar < > dinesh.ku...@enterprisedb.com> wrote: > >> Hi Dave, >> >> Further to our discussion on this issue, it seems the problem is with the >> length of the text in the grid. Thanks for your guidance. >> >> In windows 7, if the length of a string in the grid exceeds "4679", then >> it's not able to render the values properly. >> >> SELECT substring(geom::text from 1 FOR 4679) FROM plz; >> >> If i execute the above statement, then it's showing all the 16 values. >> But this is not the case in the CentOS. >> >> Kindly let me know how to proceed on this issue. >> >> 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, Aug 8, 2013 at 1:14 PM, Dinesh Kumar < >> dinesh.ku...@enterprisedb.com> wrote: >> >>> >>> On Wed, Aug 7, 2013 at 11:53 PM, Christian H. Bruhn <br...@arcor.de>wrote: >>> >>>> am Mittwoch, 7. August 2013 um 09:59 schrieb Dinesh Kumar: >>>> >>>> > I have just done a quick test case with the given steps, but i am not >>>> able >>>> > to reproduce the case in Cent OS6.0. In CentOS 6, i am getting all >>>> the 16 >>>> > non null grid values and 2 null values. Would you mind to share the >>>> >>>> Yes I think its only a problem under Windows 7 (64 Bit). I tried it >>>> with Ubuntu 12.10 and also Windows XP, but there was no problem. I >>>> also made also a complete new installation in a new VM with Windows 7 >>>> and there I have the same error. >>>> >>>> Thanks Christian. >>> >>> We are able to reproduce this in windows 7. We will trying to find the >>> root cause and it's fix. >>> >>> > query/steps what you have performed in pgAdmin. >>>> >>>> Nothing special. Just show the data or made a simple "SELECT * FROM >>>> plz;" >>>> >>>> http://imageshack.us/photo/my-images/843/j7zv.png/ >>>> http://imageshack.us/photo/my-images/706/9vzx.png/ >>>> >>>> Christian >>>> >>>> >>> >>> >>> 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> >>> >>> >>> >>>> >>>> >>>> -- >>>> Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) >>>> To make changes to your subscription: >>>> http://www.postgresql.org/mailpref/pgadmin-support >>>> >>> >>> >> > -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
