There is an important detail that you should not miss when working with MySQL generated columns based on a JSON column
I’ve been working with the cool feature of MySQL where you can generate fields based on data in a JSON column. In this blogpost, I explain a bit about how this works.
One of the weak points in our Rancher 1 cluster has always been the database. Because databases and docker (due to the persistence issues) has always been an issue, we solved that by installing a MySQL server on the same droplet that our Rancher server was running on. While it worked fine, it was always…
Just a quick blogpost today about Solr. If I help someone with this post, good. If I help myself to remember this, good. In a project I’m currently working on I’m stuck with a legacy database where I can’t change the fields for fear of breaking a legacy application that is using the same data.…
I am still in the process of moving the sites from my old host to DreamHost. One of the sites is one I host for a fellow artist. After doing the regular MySQL dump, and loading this dump into the new database, all unicode characters were, to say it in proper english, fucked up. Luckily,…
I’m currently working with extending an existing application, so I’m working with a database someone else designed. Not a problem usually, except for the fact that this person chose to use the TIMESTAMP fieldtype, which I usually don’t use. Now, when I think of a timestamp, I automatically think of a Unix Timestamp, which is…