On Wed, Jul 03, 2019 at 02:10:55PM +0200, Karsten Hilbert 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.
Sorry, I didn't read properly:
>>> What happens to >>data<< if I simple redefine the table field
Nothing should happen to the data.
But:
> There may be functions in triggers or for direct use which
> rely on the assumption that it be 60 chars max.
:)
Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
