MySQL and JSON data
MySQL has historically been rather loose with data comparisons. While it has improved, this doesn't feel much different.
MySQL has historically been rather loose with data comparisons. While it has improved, this doesn't feel much different.
A year ago yesterday, the world lost Stephen Hawking; I remember waking up and hearing the news, and how it felt as if my world had shifted under my feet. A year ago today, my world shattered.
I've been a user of TaskWarrior for a long time, though not always seriously, and I recently started using TimeWarrior with it so that I can keep track of the time that I spend on tasks. This is a tale about how it all went wrong, but because of some really smart choices by the original developers, it all came back in the end.
This one is a full on face-palm of fun: A client recently redirected one site that we didn't host to one that we do. At some point, Googlebot had indexed their old site and had URLs to files on the site, and fetching those URLs took down our site.
Last week we ran in to an issue wherein MySQL stopped allowing logins from several of our user accounts. This post documents how that happened, and what you might need to prevent this issue going forward.
I, like most developers, am lazy (which is apparently a virtue!) and recently needed to remove a bunch of CREATE TABLE statements from a mysqldump. The vim macro below is how I accomplished that task.
I've been working for the last six months to build a long-term roadmap for the products at my nonprofit technology company in North Carolina, and one of the products I discovered during my research into data segmentation and analytics tools was Segment.com. I was pretty sure when I found it that I had found something substantially valuable to nonprofits, but it took me a free trial and few months to really wrap my head around the value it brings to any startup or small business struggling with "app fatigue".