<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>MySQL-dump - Comments</title>
    <link>http://mysqldump.azundris.com/</link>
    <description>MySQL-dump - my life with MySQL</description>
    <dc:language>en</dc:language>
    <admin:errorReportsTo rdf:resource="mailto:mysqldump@mysqldump.azundris.com" />
    <generator>Serendipity 1.2-beta2 - http://www.s9y.org/</generator>
    
    <image>
        <url>http://mysqldump.azundris.com/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: MySQL-dump - Comments - MySQL-dump - my life with MySQL</title>
        <link>http://mysqldump.azundris.com/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>santosh: An InnoDB tutorial</title>
    <link>http://mysqldump.azundris.com/archives/76-An-InnoDB-tutorial.html#c2234</link>
            <category></category>
    
    <comments>http://mysqldump.azundris.com/archives/76-An-InnoDB-tutorial.html#comments</comments>
    <wfw:comment>http://mysqldump.azundris.com/wfwcomment.php?cid=76</wfw:comment>

    

    <author>nospam@example.com (santosh)</author>
    <content:encoded>
    I have a problem in deleting the child table row from my application using unique id. when I am using the command prompt it is getting deleted. But, from my application when I am deleting a post the result is 1 but, when I am refreshing the post.php I can see the post which I have tried to delete 
    </content:encoded>

    <pubDate>Mon, 21 Jul 2008 11:13:57 +0200</pubDate>
    <guid isPermaLink="false">http://mysqldump.azundris.com/archives/76-guid.html#c2234</guid>
    
</item>
<item>
    <title>Azundris: Nermalisation</title>
    <link>http://mysqldump.azundris.com/archives/20-Nermalisation.html#c2233</link>
            <category></category>
    
    <comments>http://mysqldump.azundris.com/archives/20-Nermalisation.html#comments</comments>
    <wfw:comment>http://mysqldump.azundris.com/wfwcomment.php?cid=20</wfw:comment>

    

    <author>nospam@example.com (Azundris)</author>
    <content:encoded>
    The point is that you have the option to not do, but then you&#039;ll be in a world of pain. The point is also to show that if you do it, how to do it. A more technical approach is here:&lt;br /&gt;
http://en.wikipedia.org/wiki/Database_normalization 
    </content:encoded>

    <pubDate>Sat, 05 Jul 2008 16:08:58 +0200</pubDate>
    <guid isPermaLink="false">http://mysqldump.azundris.com/archives/20-guid.html#c2233</guid>
    
</item>
<item>
    <title>fdask: Nermalisation</title>
    <link>http://mysqldump.azundris.com/archives/20-Nermalisation.html#c2232</link>
            <category></category>
    
    <comments>http://mysqldump.azundris.com/archives/20-Nermalisation.html#comments</comments>
    <wfw:comment>http://mysqldump.azundris.com/wfwcomment.php?cid=20</wfw:comment>

    

    <author>nospam@example.com (fdask)</author>
    <content:encoded>
    Nice little article, and I like how you&#039;ve used cats in your examples :)&lt;br /&gt;
&lt;br /&gt;
I am a little unclear what the point here is though... break tables up? 
    </content:encoded>

    <pubDate>Fri, 04 Jul 2008 15:40:45 +0200</pubDate>
    <guid isPermaLink="false">http://mysqldump.azundris.com/archives/20-guid.html#c2232</guid>
    
</item>
<item>
    <title>Salmiakki: Salmiakki - the official MySQL Drink</title>
    <link>http://mysqldump.azundris.com/archives/79-Salmiakki-the-official-MySQL-Drink.html#c2230</link>
            <category></category>
    
    <comments>http://mysqldump.azundris.com/archives/79-Salmiakki-the-official-MySQL-Drink.html#comments</comments>
    <wfw:comment>http://mysqldump.azundris.com/wfwcomment.php?cid=79</wfw:comment>

    

    <author>nospam@example.com (Salmiakki)</author>
    <content:encoded>
    150g of liquorice are enough to get the original Salmiakki taste.... you can add some more, anyway 
    </content:encoded>

    <pubDate>Sun, 08 Jun 2008 11:34:56 +0200</pubDate>
    <guid isPermaLink="false">http://mysqldump.azundris.com/archives/79-guid.html#c2230</guid>
    
</item>
<item>
    <title>mohammad: DB Designer becomes MySQL Workbench</title>
    <link>http://mysqldump.azundris.com/archives/21-DB-Designer-becomes-MySQL-Workbench.html#c2229</link>
            <category></category>
    
    <comments>http://mysqldump.azundris.com/archives/21-DB-Designer-becomes-MySQL-Workbench.html#comments</comments>
    <wfw:comment>http://mysqldump.azundris.com/wfwcomment.php?cid=21</wfw:comment>

    

    <author>nospam@example.com (mohammad)</author>
    <content:encoded>
    It&#039;s very good 
    </content:encoded>

    <pubDate>Wed, 28 May 2008 05:41:16 +0200</pubDate>
    <guid isPermaLink="false">http://mysqldump.azundris.com/archives/21-guid.html#c2229</guid>
    
</item>
<item>
    <title>delbertino: phpvikinger.org: Things that have no name</title>
    <link>http://mysqldump.azundris.com/archives/55-phpvikinger.org-Things-that-have-no-name.html#c2228</link>
            <category></category>
    
    <comments>http://mysqldump.azundris.com/archives/55-phpvikinger.org-Things-that-have-no-name.html#comments</comments>
    <wfw:comment>http://mysqldump.azundris.com/wfwcomment.php?cid=55</wfw:comment>

    

    <author>nospam@example.com (delbertino)</author>
    <content:encoded>
    In reply to &quot;stuff with no names&quot;:very informative and succinct. I am retired and need to learn to build a website for e-commerce;check dull &quot;on-line thriftshop&quot; @&quot;zmama.vstore.ca&quot; to see why I need to take control but need to learn PHP v6 now.Thanx for your precious time. 
    </content:encoded>

    <pubDate>Sun, 11 May 2008 06:34:15 +0200</pubDate>
    <guid isPermaLink="false">http://mysqldump.azundris.com/archives/55-guid.html#c2228</guid>
    
</item>
<item>
    <title>ashok: What is the difference between MySQL and Postgres?</title>
    <link>http://mysqldump.azundris.com/archives/65-What-is-the-difference-between-MySQL-and-Postgres.html#c2227</link>
            <category></category>
    
    <comments>http://mysqldump.azundris.com/archives/65-What-is-the-difference-between-MySQL-and-Postgres.html#comments</comments>
    <wfw:comment>http://mysqldump.azundris.com/wfwcomment.php?cid=65</wfw:comment>

    

    <author>nospam@example.com (ashok)</author>
    <content:encoded>
    what is the difference between MySql and PostgreSql? 
    </content:encoded>

    <pubDate>Wed, 30 Apr 2008 14:08:45 +0200</pubDate>
    <guid isPermaLink="false">http://mysqldump.azundris.com/archives/65-guid.html#c2227</guid>
    
</item>
<item>
    <title>fortunecookienotes: Fortune Cookie</title>
    <link>http://mysqldump.azundris.com/archives/67-Fortune-Cookie.html#c2226</link>
            <category></category>
    
    <comments>http://mysqldump.azundris.com/archives/67-Fortune-Cookie.html#comments</comments>
    <wfw:comment>http://mysqldump.azundris.com/wfwcomment.php?cid=67</wfw:comment>

    

    <author>nospam@example.com (fortunecookienotes)</author>
    <content:encoded>
    What a random fortune, who knows what it means. My favorite random fortune cookie note reads &quot;you will make a good laywer.&quot; 
    </content:encoded>

    <pubDate>Wed, 09 Apr 2008 21:46:52 +0200</pubDate>
    <guid isPermaLink="false">http://mysqldump.azundris.com/archives/67-guid.html#c2226</guid>
    
</item>
<item>
    <title>Harrison Fisk: Configuring InnoDB -  An InnoDB tutorial</title>
    <link>http://mysqldump.azundris.com/archives/78-Configuring-InnoDB-An-InnoDB-tutorial.html#c2225</link>
            <category></category>
    
    <comments>http://mysqldump.azundris.com/archives/78-Configuring-InnoDB-An-InnoDB-tutorial.html#comments</comments>
    <wfw:comment>http://mysqldump.azundris.com/wfwcomment.php?cid=78</wfw:comment>

    

    <author>nospam@example.com (Harrison Fisk)</author>
    <content:encoded>
    Hi Kristian,&lt;br /&gt;
&lt;br /&gt;
I noticed a few things that are wrong with your above article.  Overall it is good however, so don&#039;t take this as complaints ;)&lt;br /&gt;
&lt;br /&gt;
1.  innodb_flush_method=O_DIRECT:  In this case, the data files are opened with O_DIRECT, but the REDO logs are not and still use fsync.&lt;br /&gt;
&lt;br /&gt;
This is due to the fact that O_DIRECT requires aligned access, but the REDO doesn&#039;t have nice always aligned access.  The data files always are accessed in 16k pages, so it is always aligned.&lt;br /&gt;
&lt;br /&gt;
2.  Background recovery in 5.0:  Only the UNDO process is done in the background, the REDO log replay will still be done prior to startup.  So the size of the log files still does impact restart time.  They are the only thing that effect recovery time now, whereas previously the size of the UNDO segments did as well.&lt;br /&gt;
&lt;br /&gt;
3. Innodb_log_waits:  This status counter is for when the innodb_log_buffer is full and needs to synchronously flushed and is not at all related to when a checkpoint needs to be done.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Feel free to catch me on IRC if you have any questions about these.  Thanks! 
    </content:encoded>

    <pubDate>Thu, 27 Mar 2008 19:17:51 +0100</pubDate>
    <guid isPermaLink="false">http://mysqldump.azundris.com/archives/78-guid.html#c2225</guid>
    
</item>
<item>
    <title>Erik: Rubyisms</title>
    <link>http://mysqldump.azundris.com/archives/72-Rubyisms.html#c2224</link>
            <category></category>
    
    <comments>http://mysqldump.azundris.com/archives/72-Rubyisms.html#comments</comments>
    <wfw:comment>http://mysqldump.azundris.com/wfwcomment.php?cid=72</wfw:comment>

    

    <author>nospam@example.com (Erik)</author>
    <content:encoded>
    Sorry, I should mention that the create transaction simply involves doing:&lt;br /&gt;
&lt;br /&gt;
content = BlogContent.new(params[:content])&lt;br /&gt;
entry = BlogEntry.new(params[:entry].merge(:content =&gt; content))&lt;br /&gt;
entry.save! 
    </content:encoded>

    <pubDate>Wed, 19 Mar 2008 15:01:13 +0100</pubDate>
    <guid isPermaLink="false">http://mysqldump.azundris.com/archives/72-guid.html#c2224</guid>
    
</item>
<item>
    <title>Erik: Rubyisms</title>
    <link>http://mysqldump.azundris.com/archives/72-Rubyisms.html#c2223</link>
            <category></category>
    
    <comments>http://mysqldump.azundris.com/archives/72-Rubyisms.html#comments</comments>
    <wfw:comment>http://mysqldump.azundris.com/wfwcomment.php?cid=72</wfw:comment>

    

    <author>nospam@example.com (Erik)</author>
    <content:encoded>
    I like to separate text and blob columns into their own models and tables, storing and managing the record content separate from its meta data.&lt;br /&gt;
&lt;br /&gt;
For example in the case of a blog I would have two models: BlogEntry and BlogContent the later having just an id and text column. This allows me to RUD the metadata separately from the content and use lazy loading of the content when needed. The only hitch is that you need to wrap the create operation in a transaction.&lt;br /&gt;
&lt;br /&gt;
This avoids many of the problems mentioned above and offers a great deal of flexibility in how the bulk of the data (the content) is managed on the back end. 
    </content:encoded>

    <pubDate>Wed, 19 Mar 2008 14:51:13 +0100</pubDate>
    <guid isPermaLink="false">http://mysqldump.azundris.com/archives/72-guid.html#c2223</guid>
    
</item>
<item>
    <title>James deville: Rubyisms</title>
    <link>http://mysqldump.azundris.com/archives/72-Rubyisms.html#c2222</link>
            <category></category>
    
    <comments>http://mysqldump.azundris.com/archives/72-Rubyisms.html#comments</comments>
    <wfw:comment>http://mysqldump.azundris.com/wfwcomment.php?cid=72</wfw:comment>

    

    <author>nospam@example.com (James deville)</author>
    <content:encoded>
    IMHO: Rails is being designed and primarily used by people with a dedicated DB. So the idea of constraining in the DB is not as important. As David H has said multiple times, if something bothers you, submit a patch.&lt;br /&gt;
&lt;br /&gt;
If you are here and unable to code in ruby for a patch you would like, let me know (james dot deville with gmail), and I&#039;ll even see if I can do it for you! 
    </content:encoded>

    <pubDate>Wed, 27 Feb 2008 04:47:51 +0100</pubDate>
    <guid isPermaLink="false">http://mysqldump.azundris.com/archives/72-guid.html#c2222</guid>
    
</item>
<item>
    <title>James deville: Rubyisms</title>
    <link>http://mysqldump.azundris.com/archives/72-Rubyisms.html#c2221</link>
            <category></category>
    
    <comments>http://mysqldump.azundris.com/archives/72-Rubyisms.html#comments</comments>
    <wfw:comment>http://mysqldump.azundris.com/wfwcomment.php?cid=72</wfw:comment>

    

    <author>nospam@example.com (James deville)</author>
    <content:encoded>
    Rails only uses transactions if you ask it to. If you just do a People.find(:all), it does a select * from people, not a begin; select * from people; commit; 
    </content:encoded>

    <pubDate>Wed, 27 Feb 2008 04:33:16 +0100</pubDate>
    <guid isPermaLink="false">http://mysqldump.azundris.com/archives/72-guid.html#c2221</guid>
    
</item>
<item>
    <title>James: A quick tour of DRBD</title>
    <link>http://mysqldump.azundris.com/archives/56-A-quick-tour-of-DRBD.html#c2220</link>
            <category></category>
    
    <comments>http://mysqldump.azundris.com/archives/56-A-quick-tour-of-DRBD.html#comments</comments>
    <wfw:comment>http://mysqldump.azundris.com/wfwcomment.php?cid=56</wfw:comment>

    

    <author>nospam@example.com (James)</author>
    <content:encoded>
    DRBD acts like a mirror of a disk only instead of copying to a local disk on the server it copies accross the network to another server. So as soon as you make a change to the primary server it is written to the disk of the failover server. 
    </content:encoded>

    <pubDate>Tue, 26 Feb 2008 00:00:58 +0100</pubDate>
    <guid isPermaLink="false">http://mysqldump.azundris.com/archives/56-guid.html#c2220</guid>
    
</item>
<item>
    <title>Nilesh: Configuring InnoDB -  An InnoDB tutorial</title>
    <link>http://mysqldump.azundris.com/archives/78-Configuring-InnoDB-An-InnoDB-tutorial.html#c2219</link>
            <category></category>
    
    <comments>http://mysqldump.azundris.com/archives/78-Configuring-InnoDB-An-InnoDB-tutorial.html#comments</comments>
    <wfw:comment>http://mysqldump.azundris.com/wfwcomment.php?cid=78</wfw:comment>

    

    <author>nospam@example.com (Nilesh)</author>
    <content:encoded>
    Hi,&lt;br /&gt;
 I have been working on an MySQL DBA Dashboard. The Dashboard currently has basic information from the information schema.&lt;br /&gt;
&lt;br /&gt;
 Would like your opinion to improve and make it useful, for e.g to add DB performance metrics etc, but not sure where this information would be available.&lt;br /&gt;
&lt;br /&gt;
Your opinion is highly regarded and  will really appreciate if you could point me to some resources on this.&lt;br /&gt;
( njethwa @ gma!l . com)&lt;br /&gt;
Regards&lt;br /&gt;
Nilesh&lt;br /&gt;
MySQL Dashboards 
    </content:encoded>

    <pubDate>Tue, 19 Feb 2008 19:58:52 +0100</pubDate>
    <guid isPermaLink="false">http://mysqldump.azundris.com/archives/78-guid.html#c2219</guid>
    
</item>

</channel>
</rss>