News for hackers. Stuff that matters.

A comment on Common mistakes in PostgreSQL. Parent comment

Re:Common mistakes in PostgreSQL by breakingcups on Friday May 03, 2019 @09:15AM (#19818090)
Until a troll uploads the Bee Movie script as a first name.
[ Parent | on HN ]
Re:Common mistakes in PostgreSQL by colanderman on Friday May 03, 2019 @09:30AM (#19818205)
Use `CHECK length(the_column) < some_maximum`. It has the benefit that you can change it without having to redefine views.
[ Parent | on HN ]
Re:Common mistakes in PostgreSQL by komali2 on Friday May 03, 2019 @10:18AM (#19818639)
Woah that's my go-to, I had no idea I wasnt the only one doing this.
[ Parent | on HN ]
Re:Common mistakes in PostgreSQL by jmt_ on Friday May 03, 2019 @10:25AM (#19818721)
The Bee Movie is truly the lorem ipsum of tomorrow.
[ Parent | on HN ]
Re:Common mistakes in PostgreSQL by sanderjd on Friday May 03, 2019 @11:31AM (#19819286)
... or the Bee Movie as a base64 encoded string.
[ Parent | on HN ]
Re:Common mistakes in PostgreSQL by ralusek on Friday May 03, 2019 @01:23PM (#19820303)
But every time there's a "b" in the output string, the lyrics to All Star are added in plaintext.
[ Parent | on HN ]
Re:Common mistakes in PostgreSQL by knodi123 on Friday May 03, 2019 @03:03PM (#19821269)
we call this beecryption
[ Parent | on HN ]
Re:Common mistakes in PostgreSQL by ralusek on Friday May 03, 2019 @05:18PM (#19822376)
bcrypt
[ Parent | on HN ]
Re:Common mistakes in PostgreSQL by kevin_thibedeau on Friday May 03, 2019 @05:40PM (#19822535)
... of a scrypt
[ Parent | on HN ]