Postgres data types you should consider using

Re:Postgres data types you should consider using by glancast on Wednesday August 29, 2018 @05:15PM (#17872123)

For those (like me) who are wary of enums, it's very simple to create a tiny table with one column of distinct string values. Future-proof and serves the same function if you add not-null foreign key constraints to your dependent tables.

[ Parent | on HN ]

Re:Postgres data types you should consider using by jdfellow on Wednesday August 29, 2018 @07:04PM (#17872855)

I may be mistaken, but I believe under the hood Postgres enums work in a very similar way to this, only the strings are interred instead of duplicated across your tables.

[ Parent | on HN ]

Re:Postgres data types you should consider using by glancast on Thursday August 30, 2018 @02:36PM (#17879435)

Yes, that's true. I'm paying the small duplication cost in exchange for removing enums' cumbersome limitations. Not saying I never use them, but I usually end up regretting it when I do :)

[ Parent | on HN ]