From: | Erwin Brandstetter <brandstetter(at)falter(dot)at> |
---|---|
To: | dpage(at)postgresql(dot)org |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: edit grid: linebreak added to data |
Date: | 2006-11-13 15:34:10 |
Message-ID: | 45589072.8000004@falter.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
dpage(at)postgresql(dot)org wrote:
> Erwin Brandstetter wrote:
>> dpage(at)postgresql(dot)org wrote:
>>> And in case you were wondering, we use the wxTE_RICH flag to allow
>>> the control to hold more than 64KB of text (though I do wonder if
>>> that's actually still required).
>>
>> Now that you have disabled editing bytea, it might not be needed
>> anymore?
>
> Why? Text/varchar can hold up to a gigabyte iirc.
Right. But who would possibly dream of editing gigabytes in pgAdmin? And
don't you have an option "Max. characters per column" in place, which
could prevent excess data?
> As for date & timestamp, those will hardly grow beyond 64k. :)
>
> True - it hadn't crossed my mind that they shouldn't realy have used
> the multiline editor anyway (too early, no coffee!!). I've change
> dates, times, timestamps and intervals to use a single line editor.
>
> I'll send you the regulation .exe update offlist :-)
I'll look into it.
Regards
Erwin
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2006-11-13 15:40:39 | Re: edit grid: linebreak added to data |
Previous Message | Dave Page | 2006-11-13 15:01:45 | Re: edit grid: linebreak added to data |