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