Fix your Strings in PostgreSQL
summary
Shows concrete fixes: convert freeform columns to proper types (dates, integers, arrays), add a phone domain with a regex so bad formats fail, and split clients into a client table plus bookings so one-per-person-per-day constraint works. Demonstrates array functions and intersection for interests, uses unaccent to normalize characters, then fuzzystrmatch with levenshtein difference and SOUNDEX scores to find likely duplicates. All examples run in PostgreSQL and the constraints and helper functions successfully prevent or surface the messy rows.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 0:23The problem with strings
- 7:12How can we fix these problems?
- 9:32Demo
- 28:49From chaos to order
related talks
49mSELECT 'amazing features' FROM "postgresql"
29mSELECT 'amazing_features' FROM "postgresql"
45mSELECT 'amazing_features' FROM "postgresql"
25mJSON in PostgreSQL - evil data type or just needs to be tamed?
46mUse PostgreSQL to Step Up Your Game
33mPostgres, the Best Tool You're Already Using
31mSimplifying the Top Complexities While Migrating From Oracle to PostgreSQL
42mPostgreSQL Tips & Tricks For App Devs