From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Doug Fields <dfields-pg-general(at)pexicom(dot)com> |
Cc: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: ERROR: value too long for type character |
Date: | 2002-05-22 00:49:08 |
Message-ID: | 20020521174657.R28822-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 21 May 2002, Doug Fields wrote:
>
> > > Do you know how I can tell it to "silently truncate" the data as I believe
> > > it used to?
> >
> >Is there a reason you can't just use TEXT? It will be stored the same
> >internally...
>
> The only reason being that I don't want to waste space storing arbitrarily
> long pieces of information.
>
> I was not aware that TEXT is just as (in)efficient as VARCHAR, though. If
> that is truly the case, I will consider using TEXT in some places, but only
> when I am very careful in the INSERT and UPDATE clauses so as not to store
> too long things.
>
> >But the most obvious way I can think of to do what you're asking is
> >to define a rule to replace the value inserted with a call to
> >substring().
>
> So, basically:
>
> 1) There's absolutely no way to get back the 7.1.3 "silent truncation"
> behavior (which is, IMO, stupid, I like the non-standard truncation behavior)
You could do this via a text column and a before trigger which might work
better than a rule, but I haven't tried either, so...
From | Date | Subject | |
---|---|---|---|
Next Message | Victor Manuel Torres Aguirre | 2002-05-22 00:50:14 | PostgreSQL+Access97+Linux: How to.. |
Previous Message | Soon-Son Kwon | 2002-05-22 00:12:59 | Re: too many idle processes |