Sounds good to me. This has been a bug-bear for me for a long time too.
-----Original Message-----
From: pgadmin-support-owner@postgresql.org [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of Dave Page
Sent: Monday, January 07, 2008 10:11 AM
To: Kieran McCusker
Cc: pgadmin-support@postgresql.org; pgadmin-hackers@postgresql.org
Subject: Re: [pgadmin-support] Text column with large amounts of data
On 04/01/2008, Dave Page <dpage@postgresql.org> wrote:
> On 04/01/2008, Kieran McCusker <kieran.mccusker@kwest.info> wrote:
> > Dave
> >
> > Does Max characters per column work in 1.8.1? Whatever I set the limit does
> > not seem to affect text fields?
>
> It should do, but maybe it got broken :-(. I'll add it to my todo list.
Yes, it did get broken quite a while back. The attached patch will fix
it again, but this is potentially problematic because
a) it's a non-obvious change in behaviour over last last few releases
b) the default setting means it will be turned on (because the default
value is 256, not zero).
c) we don't know if any data is actually truncated until the cell is
rendered, meaning we cannot popup a warning at query completion time.
The safest option seems to me to be to apply the patch to trunk, and
change the default to zero, using a different config option to ensure
we don't pickup the old default form prior installations.
Thoughts anyone?
/D
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.