<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Mysql on fplanque.com [EN]</title>
    <link>https://www.fplanque.com/tags/mysql/</link>
    <description>Recent content in Mysql on fplanque.com [EN]</description>
    <generator>Hugo -- 0.134.3</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 12 Jun 2022 17:41:12 +0000</lastBuildDate>
    <atom:link href="https://www.fplanque.com/tags/mysql/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to manage MySQL binary log space (Debian)</title>
      <link>https://www.fplanque.com/tech/linux/mysql-binary-log-space-debian/</link>
      <pubDate>Mon, 15 Oct 2007 00:27:00 +0000</pubDate>
      <guid>https://www.fplanque.com/tech/linux/mysql-binary-log-space-debian/</guid>
      <description>So it turns out that what is filling up my root partition is my MySQL binary logs.A collection of fat files in /var/log/mysql ...So I had several options:  Move the logs to a different partition  Increase the size of the root partition  D&amp;amp;hellip;</description>
    </item>
    <item>
      <title>How to check what MySQL version I am using?</title>
      <link>https://www.fplanque.com/tech/databases/mysql/what-s-my-mysql-version-number/</link>
      <pubDate>Mon, 01 Oct 2007 16:44:00 +0000</pubDate>
      <guid>https://www.fplanque.com/tech/databases/mysql/what-s-my-mysql-version-number/</guid>
      <description>In order to determine which MySQL version you&amp;#39;re running you can type the following command: mysql -V
Sample results: # mysql -V mysql  Ver 14.7 Distrib 4.1.11, for pc-linux-gnu (i386)
# mysql -V mysql  Ver 14.12 Distrib 5.0.32, for pc-linux-gnu&amp;amp;hellip;</description>
    </item>
    <item>
      <title>Charsets in MySQL 4.1</title>
      <link>https://www.fplanque.com/tech/databases/mysql/charsets-in-mysql-4-1/</link>
      <pubDate>Mon, 03 Oct 2005 14:40:00 +0000</pubDate>
      <guid>https://www.fplanque.com/tech/databases/mysql/charsets-in-mysql-4-1/</guid>
      <description>Once you start messing around with charsets in MySQL you eventually get to a situation where the default charset for your database is UTF-8 but you want to import old backups in their own charset, for instance ISO-LATIN-1. But when you import it, MySQL&amp;amp;hellip;</description>
    </item>
    <item>
      <title>MySQL Data Integrity Enforcement Caveats</title>
      <link>https://www.fplanque.com/tech/databases/mysql/mysql-data-integrity-enforcement-caveats/</link>
      <pubDate>Thu, 31 Mar 2005 17:21:00 +0000</pubDate>
      <guid>https://www.fplanque.com/tech/databases/mysql/mysql-data-integrity-enforcement-caveats/</guid>
      <description>Okay, I desperately lack time to write full articles posts lately, so I&amp;#39;m going to make this quick! :P Background: Suppose you have a table named Now, here&amp;#39;s my point: from my experience I have found that a hell lot of things can go wrong when you try&amp;amp;hellip;</description>
    </item>
    <item>
      <title>MySQL features by version breakdown</title>
      <link>https://www.fplanque.com/tech/databases/mysql/mysql-features-by-version-breakdown/</link>
      <pubDate>Mon, 06 Dec 2004 19:55:00 +0000</pubDate>
      <guid>https://www.fplanque.com/tech/databases/mysql/mysql-features-by-version-breakdown/</guid>
      <description>I could not find anything like this on the net, so I thought I&amp;#39;d make my own chart and share it... ;) MySQL version 3.23.58 &#43;InnoDB 4.0.22 4.1.7 5.0 Release date 11-sept-03 27-oct-04 23-oct-04 not stable yet Row level locking yes yes yes yes&amp;amp;hellip;</description>
    </item>
    <item>
      <title>Exporting MySQL databases</title>
      <link>https://www.fplanque.com/tech/databases/mysql/exporting-mysql-databases/</link>
      <pubDate>Fri, 03 Dec 2004 17:51:00 +0000</pubDate>
      <guid>https://www.fplanque.com/tech/databases/mysql/exporting-mysql-databases/</guid>
      <description>PhpMyAdmin does a pretty decent job at exporting MySql database with their structure and/or their data to a plain SQL file. One thing bugged me though: it encloses every table/column/whatever name in backquotes like in Life is good! :D</description>
    </item>
    <item>
      <title>Another lousy PHP/MySQL /charset issue...</title>
      <link>https://www.fplanque.com/tech/databases/mysql/another-lousy-php-mysql-charset-issue/</link>
      <pubDate>Fri, 03 Dec 2004 17:01:00 +0000</pubDate>
      <guid>https://www.fplanque.com/tech/databases/mysql/another-lousy-php-mysql-charset-issue/</guid>
      <description>We had this quite interesting situation at work today: I export an UTF-8 MySQL database into an UTF_8 SQL file. I *binary* FTP the file over to him. He plays the SQL in PHPmyAdmin all configured for UTF-8. He then checks the data in PHPmyAdmin: special&amp;amp;hellip;</description>
    </item>
    <item>
      <title>Using PHP 4.3.8 with MySQL 4.1</title>
      <link>https://www.fplanque.com/tech/databases/mysql/using-php-4-3-8-with-mysql-4-1/</link>
      <pubDate>Wed, 06 Oct 2004 14:52:00 +0000</pubDate>
      <guid>https://www.fplanque.com/tech/databases/mysql/using-php-4-3-8-with-mysql-4-1/</guid>
      <description>Running an app under PHP 4.3.8 and trying to connect to a MySQL 4.1 database can be pretty frustrating. By default it gives you a message like this: &amp;#34;Client does not support authentication protocol requested by server; consider upgrading MySQL client&amp;#34;.&amp;amp;hellip;</description>
    </item>
    <item>
      <title>mySQL &amp; Oracle</title>
      <link>https://www.fplanque.com/tech/databases/mysql-and-oracle/</link>
      <pubDate>Sat, 26 Jul 2003 15:36:00 +0000</pubDate>
      <guid>https://www.fplanque.com/tech/databases/mysql-and-oracle/</guid>
      <description>(via Cédric) Jim Gray [Links gone]: &amp;#34;Larry Ellison announced that Oracle is now running entirely on Linux. But he didn&amp;#39;t say, &amp;#34;Incidentally we&amp;#39;re going to run all of Oracle on MySQL on Linux.&amp;#34; If you just connected the dots, that would be&amp;amp;hellip;</description>
    </item>
    <item>
      <title>Date Arithmetic With MySQL</title>
      <link>https://www.fplanque.com/tech/databases/mysql/date-arithmetic-with-mysql/</link>
      <pubDate>Sun, 13 Jul 2003 00:22:00 +0000</pubDate>
      <guid>https://www.fplanque.com/tech/databases/mysql/date-arithmetic-with-mysql/</guid>
      <description>MySQL offers pretty useful functions when you want to manipulate days: You can add a time interval to a date value with ADDDATE() or DATE_ADD() You can subtract a time interval from a date value witf DATE_SUB() You can find the interval between two&amp;amp;hellip;</description>
    </item>
    <item>
      <title>Commodity databases getting serious (slowly)</title>
      <link>https://www.fplanque.com/tech/databases/mysql/commodity-databases-getting-serious-slowly/</link>
      <pubDate>Fri, 11 Jul 2003 17:35:00 +0000</pubDate>
      <guid>https://www.fplanque.com/tech/databases/mysql/commodity-databases-getting-serious-slowly/</guid>
      <description>mySQL has been planing to implement stored procedures and triggers in mySQL 5 for some time now... But lately, it looks like it&amp;#39;s just gonna get better than expected... Via Simon Willison (great blog!), from chromatic&amp;#39;s wrap-up of OSCON day 3: Brian&amp;amp;hellip;</description>
    </item>
    <item>
      <title>mySQL 3.23 is making me sick!</title>
      <link>https://www.fplanque.com/tech/databases/mysql/mysql-3-23-is-making-me-sick/</link>
      <pubDate>Thu, 29 May 2003 21:49:00 +0000</pubDate>
      <guid>https://www.fplanque.com/tech/databases/mysql/mysql-3-23-is-making-me-sick/</guid>
      <description>No referential integrity No transactions (at least not enabled by default so hosting providers would have them) No subqueries in DELETE statements No UNION statement (can you believe it?) and of course no triggers of any kind... Not that I think mySQL&amp;amp;hellip;</description>
    </item>
    <item>
      <title>mySQL DISTINCT FUNCTION(...) bug</title>
      <link>https://www.fplanque.com/tech/databases/mysql/mysql-distinct-function-bug/</link>
      <pubDate>Sat, 10 May 2003 22:10:00 +0000</pubDate>
      <guid>https://www.fplanque.com/tech/databases/mysql/mysql-distinct-function-bug/</guid>
      <description>Looks like mySQL is not able to to perform the DISTINCT selection in cases like this: SELECT DISTINCT YEAR(post_date), MONTH(post_date) FROM whatever1 INNER JOIN whatever2 ON field1 = field2 ORDER BY post_date This can be worked around, but it seems&amp;amp;hellip;</description>
    </item>
  </channel>
</rss>
