“If you're adding a nullable column, it doesn't require to do a lot more competition at the backend, and it doesn't require any schema changes”

Sahil Walia · Software Engineering Radio - the podcast for professional software developers · Sahil Walia on Schema Changes and Data Migrations

Play from 10:55
10:55

Audio streams from the publisher’s own feed. Verbatim does not host or copy it.

What was described

state that adding a nullable column is a safe schema change even with downstream consumers

Said nearby on the same subject

“One column had less than 2 percent of the values populated, and it was initially assumed those don't bring value, but later it was realized ... downstream jobs started breaking”
SW
Sahil Walia
Software Engineering Radio - the podcast for professional software developers ·
Hard number <2% populated values Share this moment
“If you have a risk register now, you could think of adding a column called Opportunities.”
JM
Jim Moran
The ISO Review Podcast ·
Data play Share this moment
“You will write ahead logs in Postgres or binlog in MySQL… replay the changes into a new system when the new schema… essentially zero application code changes.”
SW
Sahil Walia
Software Engineering Radio - the podcast for professional software developers ·
Why it worked Share this moment
“I made a column of all the worst things that could happen… then a column for how to minimize each… then a column for how to get back quickly”
TF
Tim Ferriss
Tony Robbins Podcast Daily ·
How they work Share this moment

Moments like this, every Monday

The strongest new moments on your topics, in the speakers' own words. Free for three topics.

No card. No password. One-click unsubscribe.

Track a competitor?

Pro watches up to 25 names or phrases and emails you the morning after they are said.

See Pro, $29 a month

Verbatim quotes a short extract and links to the episode; the episode belongs to its publisher. Remove a show.