<?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>Kurinchi Blogger Scribbles ... &#187; my.cnf</title>
	<atom:link href="http://kurinchilamp.kurinchilion.com/tag/my-cnf/feed" rel="self" type="application/rss+xml" />
	<link>http://kurinchilamp.kurinchilion.com</link>
	<description>On Open Source Technologies</description>
	<lastBuildDate>Mon, 02 Jan 2012 06:14:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Linux: Case sensitive MySQL table names</title>
		<link>http://kurinchilamp.kurinchilion.com/2011/07/linux-case-sensitive-mysql-table-names.html</link>
		<comments>http://kurinchilamp.kurinchilion.com/2011/07/linux-case-sensitive-mysql-table-names.html#comments</comments>
		<pubDate>Thu, 21 Jul 2011 00:11:29 +0000</pubDate>
		<dc:creator>kurinchilamp</dc:creator>
				<category><![CDATA[LINUX]]></category>
		<category><![CDATA[MySql]]></category>
		<category><![CDATA[lower_case_table_names]]></category>
		<category><![CDATA[my.cnf]]></category>
		<category><![CDATA[mysql case sensitive]]></category>
		<category><![CDATA[mysql table not found]]></category>
		<category><![CDATA[sql case sensitive error]]></category>

		<guid isPermaLink="false">http://kurinchilamp.kurinchilion.com/?p=909</guid>
		<description><![CDATA[When transitioning MySQL database from Windows to Linux, users often encounter issues related to case-sensitiveness. Windows is case-insensitive and Linux is case-sensitive. In such scenarios when a database call is made after the application migration happens, users often run into errors which can send them in circles between the migration servers. Solution to this problem [...]]]></description>
			<content:encoded><![CDATA[<p>When transitioning MySQL database from Windows to Linux, users often encounter issues related to case-sensitiveness.  Windows is case-insensitive and Linux is case-sensitive. </p>
<p>In such scenarios when a database call is made after the application migration happens, users often run into errors which can send them in circles between the migration servers.</p>
<p>Solution to this problem is to add a single line of text under <strong>my.cnf</strong> (MySQL configuration file) under <em>[mysqld]</em><strong><span id="more-909"></span></p>
<p><strong>lower_case_table_names=1</strong></p>
<p><strong>$ whereis my.cnf</strong><br />
/etc/my.cnf</p>
<p>$ vi my.cnf<br />
&#8230;<br />
&#8230;<br />
<em>[mysqld]</em><br />
lower_case_table_names=1</p>
<p><strong>Common Errors related to this issue</strong></p>
<p>When the application is executed, users get &#8220;table not found&#8221; errors which is an indication of this error.  You can verify the error by issuing the command</p>
<p><strong>$ mysqladmin -uAdmin -pPass variables</strong></p>
<p>and check for the value of <em>lower_case_table_names</em>.</p>
]]></content:encoded>
			<wfw:commentRss>http://kurinchilamp.kurinchilion.com/2011/07/linux-case-sensitive-mysql-table-names.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MySQL: Default collation latin1_swedish_ci (swedish case insensitive)</title>
		<link>http://kurinchilamp.kurinchilion.com/2011/03/mysql-default-collation-latin1_swedish_ci-swedish-case-insensitive.html</link>
		<comments>http://kurinchilamp.kurinchilion.com/2011/03/mysql-default-collation-latin1_swedish_ci-swedish-case-insensitive.html#comments</comments>
		<pubDate>Sat, 26 Mar 2011 15:41:51 +0000</pubDate>
		<dc:creator>kurinchilamp</dc:creator>
				<category><![CDATA[MySql]]></category>
		<category><![CDATA[my.cnf]]></category>
		<category><![CDATA[mysql collation]]></category>
		<category><![CDATA[mysql default collation]]></category>
		<category><![CDATA[phpMyAdmin]]></category>

		<guid isPermaLink="false">http://kurinchilamp.kurinchilion.com/?p=893</guid>
		<description><![CDATA[When new fileds are created as variable characters they get stored as latin1_swedish_ci as default. To change the default collation users will have to manually select the collation of their choice from the mysql admin interface such as in the case of phpmyadmin or will have to denote it in sql queries. To make a [...]]]></description>
			<content:encoded><![CDATA[<p>When new fileds are created as variable characters they get stored as <strong>latin1_swedish_ci</strong> as default. To change the default collation users will have to manually select the collation of their choice from the mysql admin interface such as in the case of <em>phpmyadmin</em> or will have to denote it in sql queries.</p>
<p>To make a specific collation as the default, other option to give mysql an indication of it by having the needed collation name in <strong>my.cnf (mysql configuration)</strong> as shown below</p>
<p><strong>Edit my.cnf: </strong><br />
<em>[mysqld]<br />
collation_server=latin1_general_ci</em><br />
<span id="more-893"></span><br />
<em>MySql command to set collation type when creating database is given below:</em></p>
<p><strong>Latin1 encoding</strong><br />
CREATE DATABASE sampledb DEFAULT CHARACTER SET latin1 COLLATE latin1_general_ci;</p>
<p><strong>UTF-8 encoding</strong><br />
CREATE DATABASE sampledb DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;</p>
<p>Once the encoding for the database is set, fields associated with the tables in our new database will take up default collation as the one set during the database creation.</p>
]]></content:encoded>
			<wfw:commentRss>http://kurinchilamp.kurinchilion.com/2011/03/mysql-default-collation-latin1_swedish_ci-swedish-case-insensitive.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MySQL: Can&#8217;t connect to local MySQL server through socket &#8216;/var/run/mysqld/mysqld.sock&#8217;</title>
		<link>http://kurinchilamp.kurinchilion.com/2010/02/mysql-cant-connect-to-local-mysql-server-through-socket-varrunmysqldmysqld-sock.html</link>
		<comments>http://kurinchilamp.kurinchilion.com/2010/02/mysql-cant-connect-to-local-mysql-server-through-socket-varrunmysqldmysqld-sock.html#comments</comments>
		<pubDate>Fri, 05 Feb 2010 08:27:25 +0000</pubDate>
		<dc:creator>kurinchilamp</dc:creator>
				<category><![CDATA[LINUX]]></category>
		<category><![CDATA[MySql]]></category>
		<category><![CDATA[my.cnf]]></category>
		<category><![CDATA[mysql socket error]]></category>
		<category><![CDATA[netstat]]></category>

		<guid isPermaLink="false">http://kurinchilamp.kurinchilion.com/?p=751</guid>
		<description><![CDATA[Reason why this error might occur: i) Incomplete MySQL implementation ii) MySQL setting mis-configuration Solution: root@myserver:/# vi /etc/mysql/my.cnf Comment out the below line in my.cnf file to make MySQL listen on ALL interfaces #bind-address = 127.0.0.1 root@myserver:/# netstat -tap &#124; grep mysql tcp 0 0 *:mysql *:* LISTEN 17785/mysqld Note that above line which indicates [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Reason why this error might occur:</strong></p>
<p>i) Incomplete MySQL implementation<br />
ii) MySQL setting mis-configuration</p>
<p><strong>Solution:</strong></p>
<p><strong>root@myserver:/# vi /etc/mysql/my.cnf</strong></p>
<p>Comment out the below line in my.cnf file to make MySQL listen on ALL interfaces<br />
#bind-address = 127.0.0.1</p>
<p><strong>root@myserver:/# netstat -tap | grep mysql</strong><br />
tcp        0      0 *:mysql                 *:*                     LISTEN      17785/mysqld</p>
<p>Note that above line which indicates MySQL listening on all interfaces.</p>
]]></content:encoded>
			<wfw:commentRss>http://kurinchilamp.kurinchilion.com/2010/02/mysql-cant-connect-to-local-mysql-server-through-socket-varrunmysqldmysqld-sock.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

