Conversations with Gran about Databases

Comments 0

Share to social media

So, what’s going on in your databases world this week, young man? I paused, as always, a little unsure of what I was getting myself into. I’d been having these little “technical chats” with Gran ever since her ‘computer incident’, when a blue screen informing her of a “Fatal error: catastrophic failure“, had thrown her into such a state of panic and confusion that she’d fled the room and locked the door.

I thought it might help restore her confidence. Unwisely though, I’d strayed into explaining what I mainly did, databases, and now she wanted a weekly update. She feared for my safety, I think.

I’d had some notable early success explaining things to her, mainly with the help of the Bible. Tables in a database were no different than the money changers’ accounting tables, famously overturned (John 2:13-16). Also, I pointed out, warming to the theme, the “book, chapter and verse” reference that told us exactly what bit of the bible we meant was also used in databases, except we called it a Primary Key.

However, there seemed only so far one could go with this, and generally, the conversations had been a minefield. She’d pick up phrases, misunderstand their meaning and generally get confused.

  • Concurrency – it that like a bitcoin, one of those cache invalidation things?
  • Many-to-one correspondence – we just called it fan mail in my day.
  • Crash recovery – yes, your granddad was in hospital for weeks. I told him he should have got cyclic protection. He was nearly a flat relation.
  • Dirty pages – well I hope you didn’t look at any of them, young man. That’s a nonrepeatable read if ever I heard one.
  • Middleware – it held our stomachs in, pushed various BLOBs up or down, and concealed your input member and other external predicates.
  • Dump Device – ours was in a shed at the bottom of the garden, down the materialized path and just past our ornamental buffer pool.
  • Little endian – He was a wide character. He used to hang out with that primitive operator, Arthur TerrorBite.
  • High whisker – don’t get me started on your granddad’s eyebrows. They were bushy joins, I can tell you.
  • Hard-coded variables – wouldn’t it be better to try the easy-coded ones first?

Certain concepts, such as denormalization, or dynamic cursors, seemed so obviously fraught with difficulty that I hadn’t gone near them. I was learning to choose the battles carefully.

Now it’s your turn. What are the phrases that would confuse your gran or other base relations? Oh help, it’s caching.

Commentary Competition

Enjoyed the topic? Have a relevant anecdote? Disagree with the author? Leave your two cents on this post in the comments below, and our favourite response will win a $50 Amazon gift card. The competition closes two weeks from the date of publication, and the winner will be announced in the next Simple Talk newsletter.

Load comments

About the author

Tony Davis

See Profile

Tony Davis is an Editor with Red Gate Software, based in Cambridge (UK), specializing in databases, and especially SQL Server. He edits articles and writes editorials for both the Simple-talk.com and SQLServerCentral.com websites and newsletters, with a combined audience of over 1.5 million subscribers. You can sample his short-form writing at either his Simple-Talk.com blog or his SQLServerCentral.com author page.

As the editor behind most of the SQL Server books published by Red Gate, he spends much of his time helping others express what they know about SQL Server. He is also the lead author of the book, SQL Server Transaction Log Management.

In his spare time, he enjoys running, football, contemporary fiction and real ale.