<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
	<channel>
		<title>iamcal.com</title>
		<link>http://www.iamcal.com/</link>
		<description>All the links rom iamcal.com</description>
		<pubDate>Mon, 16 Apr 2018 22:40:25 +0000</pubDate>
		<lastBuildDate>Mon, 16 Apr 2018 22:40:25 +0000</lastBuildDate>
		<generator>http://www.iamcal.com/</generator>
		<image>
			<url>http://www.iamcal.com/images/logo.gif</url>
			<title>iamcal.com</title>
			<link>http://www.iamcal.com/</link>
		</image>

		<item>
			<title>mysql-row-per-line</title>
			<link>http://www.iamcal.com/2018-04/mysql-row-per-line/</link>
			<description>&lt;p&gt;Ideally MySQL include this in a future version of &lt;code&gt;mysqldump&lt;/code&gt;, but here&#039;s a &lt;a href=&quot;http://blog.lavoie.sl/2014/06/split-mysqldump-extended-inserts.html&quot;&gt;neat little utility&lt;/a&gt; to split extended inserts into one row per line. This allows you to use extended inserts (for &lt;em&gt;much&lt;/em&gt; faster importing of large tables) while having the ability to grep and diff rows easily.&lt;/p&gt;
</description>
			<pubDate>Mon, 16 Apr 2018 22:40:25 +0000</pubDate>
			<author>nobody@domain.com (Cal Henderson)</author>
			<guid isPermaLink="false">tag:iamcal.com,2005:/blog/10117/</guid>
		</item>
		<item>
			<title>Regexp Kung-fu</title>
			<link>http://www.iamcal.com/2013-03/regexp-kung-fu/</link>
			<description>&lt;p&gt;There are two answers guaranteed to show up on nearly every PHP question on Stack Overflow - use the mysqli/PDO extension instead of the deprecated mysql one (to avoid SQL injection), and that you can&#039;t parse HTML with regular expressions.&lt;/p&gt;

&lt;p&gt;With that in mind, my favorite two answers:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[How PDO is still vulnerable to SQL injection attacks](http://stackoverflow.com/questions/134099/are-pdo-prepared-statements-sufficient-to-prevent-sql-injection/12202218#12202218) by Anthony Ferrara&lt;/li&gt;
&lt;li&gt;[Parsing HTML with regular expressions](http://stackoverflow.com/questions/4231382/regular-expression-pattern-not-matching-anywhere-in-string/4234491#4234491) by Tom Christiansen&lt;/li&gt;
&lt;/ul&gt;
</description>
			<pubDate>Thu, 28 Mar 2013 05:10:00 +0000</pubDate>
			<author>nobody@domain.com (Cal Henderson)</author>
			<guid isPermaLink="false">tag:iamcal.com,2005:/blog/10021/</guid>
		</item>
		<item>
			<title>29th September, 6:08 am</title>
			<link>http://www.iamcal.com/2010-09/2561/</link>
			<description>&lt;p&gt;jeremy cole has finally &lt;a href=&quot;http://jcole.us/blog/archives/2010/09/28/mysql-swap-insanity-and-the-numa-architecture/&quot;&gt;solved&lt;/a&gt; the mysql swapping-for-no-reason issue. very nice work [via ph]&lt;/p&gt;
</description>
			<pubDate>Wed, 29 Sep 2010 06:08:00 +0000</pubDate>
			<author>nobody@domain.com (Cal Henderson)</author>
			<guid isPermaLink="false">tag:iamcal.com,2005:/blog/2561/</guid>
		</item>
		<item>
			<title>17th August, 4:30 am</title>
			<link>http://www.iamcal.com/2010-08/2540/</link>
			<description>&lt;p&gt;noting these down for later reference - two &lt;a href=&quot;http://www.quora.com/Why-doesnt-Quora-use-PostgreSQL&quot;&gt;excellent&lt;/a&gt; &lt;a href=&quot;http://www.quora.com/Why-does-Quora-use-MySQL-as-the-data-store-rather-than-NoSQLs-such-as-Cassandra-MongoDB-CouchDB-etc&quot;&gt;answers&lt;/a&gt; on quora from adam d&#039;angelo on why quora uses mysql instead of postgres or a nosql solution. he says everything i&#039;ve been saying for the last few years, but more eloquently&lt;/p&gt;
</description>
			<pubDate>Tue, 17 Aug 2010 04:30:00 +0000</pubDate>
			<author>nobody@domain.com (Cal Henderson)</author>
			<guid isPermaLink="false">tag:iamcal.com,2005:/blog/2540/</guid>
		</item>
		<item>
			<title>24th October, 4:18 pm</title>
			<link>http://www.iamcal.com/2009-10/2382/</link>
			<description>&lt;p&gt;a couple of interesting alternatives to phpMyAdmin, both simpler: &lt;a href=&quot;http://sqlbuddy.com/&quot;&gt;sqlbuddy&lt;/a&gt; looks like a really well done minimalist effort, while &lt;a href=&quot;http://code.google.com/p/phpminiadmin/&quot;&gt;phpMiniAdmin&lt;/a&gt; like like PMA from 10 years ago.&lt;/p&gt;
</description>
			<pubDate>Sat, 24 Oct 2009 16:18:00 +0000</pubDate>
			<author>nobody@domain.com (Cal Henderson)</author>
			<guid isPermaLink="false">tag:iamcal.com,2005:/blog/2382/</guid>
		</item>
		<item>
			<title>26th March, 6:37 pm</title>
			<link>http://www.iamcal.com/2009-03/2110/</link>
			<description>&lt;p&gt;&lt;a href=&quot;http://www.mysqlperformanceblog.com/2009/03/13/xtrabackup-03-binaries-and-stream-backup/&quot;&gt;xtrabackup&lt;/a&gt; sounds like really good news for people backing up large innodb instances. streaming backups? yes pls&lt;/p&gt;
</description>
			<pubDate>Thu, 26 Mar 2009 18:37:00 +0000</pubDate>
			<author>nobody@domain.com (Cal Henderson)</author>
			<guid isPermaLink="false">tag:iamcal.com,2005:/blog/2110/</guid>
		</item>
		<item>
			<title>31st July, 8:47 pm</title>
			<link>http://www.iamcal.com/2006-07/1226/</link>
			<description>&lt;p&gt;dathan&#039;s &lt;a href=&quot;http://mysqldba.blogspot.com/&quot;&gt;mysql blog&lt;/a&gt; is full of useful tips for people using mysql on a large scale. a kind of &quot;advanced mysql hacks&quot; book done right.&lt;/p&gt;
</description>
			<pubDate>Mon, 31 Jul 2006 20:47:00 +0000</pubDate>
			<author>nobody@domain.com (Cal Henderson)</author>
			<guid isPermaLink="false">tag:iamcal.com,2005:/blog/1226/</guid>
		</item>
		<item>
			<title>2nd July, 7:40 pm</title>
			<link>http://www.iamcal.com/2005-07/952/</link>
			<description>&lt;p&gt;mike b pointed me to this &lt;a href=&quot;http://www.zdnet.com.au/news/software/0,2000061733,39193420,00.htm&quot;&gt;bizarre article&lt;/a&gt; from IBM&#039;s daniel sabbah describes lamp as &quot;going to have to grow up at some point&quot;. err, right. because lamp clearly doesn&#039;t scale. it&#039;s not like the biggest websites in the world use it. ryan tomayko&#039;s &lt;a href=&quot;http://naeblis.cx/rtomayko/2005/05/28/ibm-poop-heads&quot;&gt;response&lt;/a&gt; is on the mark.&lt;/p&gt;
</description>
			<pubDate>Sat, 2 Jul 2005 19:40:00 +0000</pubDate>
			<author>nobody@domain.com (Cal Henderson)</author>
			<guid isPermaLink="false">tag:iamcal.com,2005:/blog/952/</guid>
		</item>
		<item>
			<title>21st January, 11:10 pm</title>
			<link>http://www.iamcal.com/2005-01/681/</link>
			<description>&lt;p&gt;backed up for later - the innodb &lt;a href=&quot;http://www.innodb.com/manual.php#innobackup&quot;&gt;hot backup script&lt;/a&gt;. faster than restoring from a dump, but more prone to corruption.&lt;/p&gt;
</description>
			<pubDate>Fri, 21 Jan 2005 23:10:00 +0000</pubDate>
			<author>nobody@domain.com (Cal Henderson)</author>
			<guid isPermaLink="false">tag:iamcal.com,2005:/blog/681/</guid>
		</item>
		<item>
			<title>21st January, 7:41 am</title>
			<link>http://www.iamcal.com/2005-01/678/</link>
			<description>&lt;p&gt;gah. f was down for 5 hours after a routine database modification revealed massive innodb corruption which had somehow replicated to the slave. after splitting the cluster, our last backup was nine days old and a few million records short. eek. so a painstaking search and destroy for bad records was conducted. stupid mysql.&lt;/p&gt;
</description>
			<pubDate>Fri, 21 Jan 2005 07:41:00 +0000</pubDate>
			<author>nobody@domain.com (Cal Henderson)</author>
			<guid isPermaLink="false">tag:iamcal.com,2005:/blog/678/</guid>
		</item>

	</channel>
</rss>
