Live data from Hacker News

Interview with Don Chamberlin, designer of SQL

mappingthejourney.com

11–15 of 15 posts

Re: Interview with Don Chamberlin, designer of SQL

#12
post #6

I've been subscribed to this podcast since his 2nd or 3rd episode. He's had some interesting guests. I think the podcast is a one-man show. He could probably use some help with mixing/production (and a new intro theme), but for a one-man show it's pretty darn good. Edit: I'm an idiot and just realized OP is the podcaster.

Thank You. Yes, I'm a one-man army and would use some help. Finding interesting guests have not been hard but doing this week after week has been hectic, but I love it. Maybe someday I can run the podcast as a team.

Re: Interview with Don Chamberlin, designer of SQL

#13
post #6

I've been subscribed to this podcast since his 2nd or 3rd episode. He's had some interesting guests. I think the podcast is a one-man show. He could probably use some help with mixing/production (and a new intro theme), but for a one-man show it's pretty darn good. Edit: I'm an idiot and just realized OP is the podcaster.

Thank You. Yes, I'm a one-man army and would use some help. Finding interesting guests have not been hard but doing this week after week has been hectic, but I love it. Maybe someday I can run the podcast as a team.

Well considering you're doing it all by yourself, you are doing an awesome job! I look forward to each new interview. I like that you give the guests time to provide an in-depth answer without peppering them with too many questions.

When you're a famous podcaster you can do a Mapping the Journey episode about Mapping the Journey! :)

Re: Interview with Don Chamberlin, designer of SQL

#15
I was glad for a transcript!

I find it interesting that the technology of the time meant it was hard to write ∀ and ∃ (though APL users seemed to go OK) and so they chose a complex syntax that reminds me of COBOL. The early database applications were business applications (SABRE being #1 I believe) so this wouldn't have been at all an unreasonable basis for SQL's syntax.

Post reply on HN