News for hackers. Stuff that matters.

A comment on Common mistakes in PostgreSQL.

Re:Common mistakes in PostgreSQL by jchampem on Friday May 03, 2019 @08:45AM (#19817887)
> If what you really need is a text field with an length limit then varchar(n) is great, but if you pick an arbitrary length and choose varchar(20) for a surname field you're risking production errors in the future when Hubert Blaine Wolfe­schlegel­stein­hausen­berger­dorff signs up for your service.

:D

[https://en.wikipedia.org/wiki/Hubert_Blaine_Wolfeschlegelste...]

[ Parent | on HN ]
Re:Common mistakes in PostgreSQL by dtjohnnyb on Friday May 03, 2019 @09:26AM (#19818174)
(The period at the end gets cut off)[https://en.wikipedia.org/wiki/Hubert_Blaine_Wolfeschlegelste...]
[ Parent | on HN ]
Re:Common mistakes in PostgreSQL by JudgeWapner on Friday May 03, 2019 @11:29AM (#19819277)
UI devs HATE him!
[ Parent | on HN ]
Re:Common mistakes in PostgreSQL by TremendousJudge on Friday May 03, 2019 @02:02PM (#19820715)
A man named Null: https://www.wired.com/2015/11/null/
[ Parent | on HN ]
Re:Common mistakes in PostgreSQL by aargh_aargh on Friday May 03, 2019 @04:45PM (#19822105)
I'd have Hubert over Bobby Tables any day!
[ Parent | on HN ]