Re: Overhead changing varchar(2000) to text
| От | Jim Nasby |
|---|---|
| Тема | Re: Overhead changing varchar(2000) to text |
| Дата | |
| Msg-id | 566F7A97.50601@BlueTreble.com обсуждение исходный текст |
| Ответ на | Re: Overhead changing varchar(2000) to text (Edson Richter <edsonrichter@hotmail.com>) |
| Ответы |
Re: Overhead changing varchar(2000) to text
|
| Список | pgsql-general |
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. -- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com
В списке pgsql-general по дате отправления: