Re: rc-1 problem with long text fields?

From: Mike(dot)Blackwell(at)rrd(dot)com
To: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
Cc: "'pgadmin-support(at)postgresql(dot)org'" <pgadmin-support(at)postgresql(dot)org>
Subject: Re: rc-1 problem with long text fields?
Date: 2004-11-19 16:18:15
Message-ID: OF6D9B1FC8.B3B003D8-ON86256F51.0058F3F7-86256F51.0059885D@rrd.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Andreas Pflug <pgadmin(at)pse-consulting(dot)de> wrote on 11/19/2004 10:07:58 AM:

> Very bad idea. If pgAdmin offers to edit the column at all, the field
> content must be complete. Anything else would lead to many bad
surprises.

Point taken. Still, going unresponsive for minutes is not a good trait
for any interactive software.

How about a size limit (configurable?) beyond which pgAdmin displays a
particular cell read-only, with truncated text or a warning in place of
the text. This would protect the user who unknowingly displays a table
entry with a large text field, while preserving the editing integrity.

Mike

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Andreas Pflug 2004-11-19 16:24:09 Re: rc-1 problem with long text fields?
Previous Message Andreas Pflug 2004-11-19 16:07:58 Re: rc-1 problem with long text fields?