Ban the Backquote

I really don’t like the backquote character (`). This is primarily due to it’s use by MySQL in internal and community tools.
MySQL allows objects, .e.g table names, column names etc to contain both reserved words and spaces, providing they are appropriately surrounded by backquotes, so tools now simply enclose everything with backquotes. Really annoying.

Last week while on a client site I was told a funny story. The CEO of a company bought an iPhone however was unable to use it at work due to the WEP key for the Wireless access in his organization includes a backquote. I’ve confirmed it, the iPhone keyboard does not have a backquote key. So now, because he is the CEO, everybody will have to change their Wireless WEP key just because of the iPhone.

But it gets better. Around midnight last Saturday between Slate Plus (for Dinner & Pool) and going down to SOHO for more drinks, Farhan had to change a cron job. As his battery was running low, he was trying to find it, you guessed it, the backquote character on his OQO . Just lucky it’s Windoze and if you can find the character map application, you can insert the character.
Rob and Michelle were on hand, and with my new EOS 40D and 50mm 1.4f lens I was able to take a series of photos without flash and without alerting my unsuspecting subjects.

Tagged with: Apple IPhone

Related Posts

My take on PyCon Australia 2026

PyCon AU 2026 held in Brisbane this week was a five day event for the Python community. With specialized tracks and dedicated tutorial and engineering days there was a wide variety of content available.

Read more

Fixing Old Software Bugs Without Thinking

I previously came across an issue in my benchmarking work where I relied on the Latency Histogram section of sysbench output. On Linux it worked fine — I generally ran my workload there, so it never mattered.

Read more

Curating DuckDB Datasets Leveraging AI

In Curated MySQL Data Sets for Realistic Testing I described datasets assembled the manual way — download, schema, load, validate, document — over hours or days per source. This post is the follow-up I promised: what changes when AI assists the same workflow, using DuckDB as the target engine and GeoNames as the first example.

Read more