I'd do this with a stored procedure. Just hand it the whole row and let
it trim the parts down to size you want trimmed down to size.
NOT autotrimming content is one of the reasons Postgresql can lay claim to
the C in ACID compliance.
On Fri, 16 May 2003, Bartlomiej Frackiewicz wrote:
> Hi,
>
> thanks for answering. Sure Perl can (handmade, DBI do not support this, or i am blindly), but i was in hope that i
cansolve this with the DB.
>
> Anyway, thanks.
>
> Bart
>
> -----Ursprüngliche Nachricht-----
> Von: Nigel J. Andrews [mailto:nandrews@investsystems.co.uk]
> Gesendet: Freitag, 16. Mai 2003 14:04
> An: Bartlomiej Frackiewicz
> Cc: pgsql-general@postgresql.org
> Betreff: Re: [GENERAL] Rollback when value too long
>
>
> On Fri, 16 May 2003, Bartlomiej Frackiewicz wrote:
>
> > Hi,
> >
> > we are using "PostgreSQL 7.3.1 on i386-pc-linux-gnu" with Perl DBI.
> >
> > Some tables where directly updated from web forms, so when the input
> > is longer than the fileld, Postgres forces a rollback. This might be
> > right, but is very angry for me. Is there a way to teach Postgres
> > that it must truncate these values?
>
> No. Can't the perl code truncate them?
>
>
> --
> Nigel Andrews
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
