Re: Overhead changing varchar(2000) to text - Mailing list pgsql-general

From Edson Richter
Subject Re: Overhead changing varchar(2000) to text
Date
Msg-id BLU436-SMTP1573CD2DE78E627282D5AB4CFEE0@phx.gbl
Whole thread Raw
In response to Re: Overhead changing varchar(2000) to text  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-general
Em 15/12/2015 00:27, Jim Nasby escreveu:
> On 12/9/15 5:43 PM, Edson Richter wrote:
>> Actually, the biggest change is that I don't have to keep another
>> constraint between app and database - if I want to increase the user
>> perceived space, now I just have to change the application (of course,
>> under the limits).
>
> For what it's worth, I usually put some limit on fields that a webapp
> can write to in the database. That way a bug in the app (or malicious
> action) can't just start allocating gigabytes of stuff in your database.

Thanks, Jim. It is a wise advice.
I really do that today, but I'll start double checking all text fields
with special care.

Kind regards,

Atenciosamente,

Edson Carlos Ericksson Richter



pgsql-general by date:

Previous
From: Paul
Date:
Subject: Trigger function, C, lookup of attribute type
Next
From: Paul
Date:
Subject: Re: Trigger function, C, lookup of attribute type