| From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Too short field |
| Date: | 2019-07-03 12:10:55 |
| Message-ID: | 20190703121055.GC2383@hermes.hilbert.loc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jul 03, 2019 at 01:56:03PM +0200, Thomas Kellerer wrote:
> Karl Martin Skoldebrand schrieb am 03.07.2019 um 13:30:
> > Now, we have a bug in another application that prevents an automatic
> > tool to enter certain users in the database. The organisational field
> > is varchar(60) while the actual Organisation “abbreviation” may be as
> > long as 70 characters (don’t ask why).
> >
> > What happens to data if I simple redefine the table field as
> > varchar(80) (or something, at least 70+). Does “everything” break
> > database side or can I just go on running the app as is.
>
> Nothing will break on the database size.
We don't know. There may be functions in triggers or for
direct use which rely on the assumption that it be 60 chars
max.
PostgreSQL itself won't care, that much holds.
Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karsten Hilbert | 2019-07-03 12:21:06 | Re: Too short field |
| Previous Message | Karl Martin Skoldebrand | 2019-07-03 12:02:16 | RE: Too short field |