<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>JSON on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/categories/json/</link>
    <description>Recent content in JSON on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 19 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/categories/json/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Switching to JSON Error Logging in MySQL</title>
      <link>https://ronaldbradford.com/blog/2026-06-19-switching-to-json-error-logging-in-mysql/</link>
      <pubDate>Fri, 19 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/2026-06-19-switching-to-json-error-logging-in-mysql/</guid>
      <description>You no longer need to manually parse the MySQL Error log via scripting and RegEx pattern matching. Using the component_log_sink_json component you can obtain JSON error logging for easier parsing.</description>
    </item>
  </channel>
</rss>
