<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>MySQL &#8211; BTA Blog</title>
	<atom:link href="https://www.businesstechnologyassociates.com/blog/category/technology/mysql/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.businesstechnologyassociates.com/blog</link>
	<description>Weblog about business and technology issues</description>
	<lastBuildDate>Sat, 27 Jul 2024 18:26:32 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>
	<item>
		<title>MySQL JASON_VALUE fails with a key starting with a number</title>
		<link>https://www.businesstechnologyassociates.com/blog/2024/07/mysql-jason_value-fails-with-a-key-starting-with-a-number/</link>
		
		<dc:creator><![CDATA[Dirk]]></dc:creator>
		<pubDate>Sat, 27 Jul 2024 18:26:32 +0000</pubDate>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Technology]]></category>
		<guid isPermaLink="false">https://www.businesstechnologyassociates.com/blog/?p=402</guid>

					<description><![CDATA[SELECT JSON_VALUE('{"dateTime": "2024-07-21 08:11:07 -0600", "60SecInches": 0.00, "DailyInches": 0.01, "TotalInches": 10.61}', "$.60SecInches"); MySQL said: #3143 &#8211; Invalid JSON path expression. The error is around character position 13.  That seems to point to the end of this string. "$.60SecInches" If I remove the &#8220;60&#8221; from the key, the above SELECT works. But the following works as &#8230; <p class="link-more"><a href="https://www.businesstechnologyassociates.com/blog/2024/07/mysql-jason_value-fails-with-a-key-starting-with-a-number/" class="more-link">Continue reading<span class="screen-reader-text"> "MySQL JASON_VALUE fails with a key starting with a number"</span></a></p>]]></description>
		
		
		
			</item>
		<item>
		<title>Upgrading Drupal and blocked by MySQL library version</title>
		<link>https://www.businesstechnologyassociates.com/blog/2024/02/upgrading-drupal-and-blocked-by-mysql-library-version/</link>
		
		<dc:creator><![CDATA[Dirk]]></dc:creator>
		<pubDate>Thu, 29 Feb 2024 18:48:52 +0000</pubDate>
				<category><![CDATA[Drupal]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[MySQL]]></category>
		<guid isPermaLink="false">https://www.businesstechnologyassociates.com/blog/?p=394</guid>

					<description><![CDATA[Recently I was upgrading a Drupal installation to version 9.5.11 and when in maintenance mode, received the error: 10.5.20-MariaDB-cll-lve-log The libmysqlclient driver version 3.1.21 is less than the minimum required version. Upgrade to libmysqlclient version 5.5.3 or up, or alternatively switch mysql drivers to MySQLnd version 5.0.9 or up. Since this installation was on a &#8230; <p class="link-more"><a href="https://www.businesstechnologyassociates.com/blog/2024/02/upgrading-drupal-and-blocked-by-mysql-library-version/" class="more-link">Continue reading<span class="screen-reader-text"> "Upgrading Drupal and blocked by MySQL library version"</span></a></p>]]></description>
		
		
		
			</item>
		<item>
		<title>MySQL/MariaDB needs upgrading after upgrading</title>
		<link>https://www.businesstechnologyassociates.com/blog/2021/10/mysql-mariadb-needs-upgrading-after-upgrading/</link>
		
		<dc:creator><![CDATA[Dirk]]></dc:creator>
		<pubDate>Sat, 02 Oct 2021 22:06:12 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[MySQL]]></category>
		<guid isPermaLink="false">https://www.businesstechnologyassociates.com/blog/?p=342</guid>

					<description><![CDATA[Recently I was reviewing log files for one of my servers and came across the following error message: mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'mysql'': Cannot load from mysql.proc. The table is probably corrupted (1728) mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'mydatabase'': Cannot load from mysql.proc. The table is &#8230; <p class="link-more"><a href="https://www.businesstechnologyassociates.com/blog/2021/10/mysql-mariadb-needs-upgrading-after-upgrading/" class="more-link">Continue reading<span class="screen-reader-text"> "MySQL/MariaDB needs upgrading after upgrading"</span></a></p>]]></description>
		
		
		
			</item>
		<item>
		<title>MySQL and UTF-8</title>
		<link>https://www.businesstechnologyassociates.com/blog/2011/07/mysql-and-utf-8/</link>
		
		<dc:creator><![CDATA[Dirk]]></dc:creator>
		<pubDate>Fri, 08 Jul 2011 22:50:24 +0000</pubDate>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Technology]]></category>
		<guid isPermaLink="false">http://www.businesstechnologyassociates.com/blog/?p=98</guid>

					<description><![CDATA[I recently had a problem in a web application that I created where the UTF-8 characters were not interpreted correctly by browsers.  The biggest issue was this did not happen in all instances of presenting these UTF-8 strings. After tracing the strings through several libraries, I found the culprit.  The following SQL statement was the &#8230; <p class="link-more"><a href="https://www.businesstechnologyassociates.com/blog/2011/07/mysql-and-utf-8/" class="more-link">Continue reading<span class="screen-reader-text"> "MySQL and UTF-8"</span></a></p>]]></description>
		
		
		
			</item>
		<item>
		<title>MySQL: Setting date field default to current date</title>
		<link>https://www.businesstechnologyassociates.com/blog/2011/03/mysql-setting-date-field-default-to-current-date/</link>
		
		<dc:creator><![CDATA[Dirk]]></dc:creator>
		<pubDate>Thu, 24 Mar 2011 17:43:59 +0000</pubDate>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[SQL]]></category>
		<guid isPermaLink="false">http://www.businesstechnologyassociates.com/blog/?p=59</guid>

					<description><![CDATA[In MySQL, creating a date/time stamp field that defaults to the current date/time has been a problem in the past.  MySQL restricted you to one timestamp field per table that is automatically updated with the current date/time.  Early versions of MySQL allowed multiple updating timestamp fields contrary to the specification, but this was &#8220;fixed&#8221; in &#8230; <p class="link-more"><a href="https://www.businesstechnologyassociates.com/blog/2011/03/mysql-setting-date-field-default-to-current-date/" class="more-link">Continue reading<span class="screen-reader-text"> "MySQL: Setting date field default to current date"</span></a></p>]]></description>
		
		
		
			</item>
	</channel>
</rss>
