<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Thoughts on Qt sql, anyone?</title>
	<atom:link href="http://www.sebruiz.net/162/feed" rel="self" type="application/rss+xml" />
	<link>http://www.sebruiz.net/162</link>
	<description></description>
	<lastBuildDate>Sun, 14 Mar 2010 23:15:18 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Seb</title>
		<link>http://www.sebruiz.net/162/comment-page-1#comment-927</link>
		<dc:creator>Seb</dc:creator>
		<pubDate>Fri, 15 Sep 2006 12:44:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.sebruiz.net/162#comment-927</guid>
		<description>@Joseph: This is not true at all.  A mysql or postgres daemon barely uses any resources on a regular desktop machine.  I think it is a common misconception that using idle processing power/resources justifies calling it bloat.  If it&#039;s not doing anything, use it!

Regardless, catering for the lowest common denominator by no means that the advantages of expert dbs is compromised.  The abstraction means each plugin could handle the requested data in a different way.</description>
		<content:encoded><![CDATA[<p>@Joseph: This is not true at all.  A mysql or postgres daemon barely uses any resources on a regular desktop machine.  I think it is a common misconception that using idle processing power/resources justifies calling it bloat.  If it&#8217;s not doing anything, use it!</p>
<p>Regardless, catering for the lowest common denominator by no means that the advantages of expert dbs is compromised.  The abstraction means each plugin could handle the requested data in a different way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Tate</title>
		<link>http://www.sebruiz.net/162/comment-page-1#comment-926</link>
		<dc:creator>Joseph Tate</dc:creator>
		<pubDate>Fri, 15 Sep 2006 12:31:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.sebruiz.net/162#comment-926</guid>
		<description>Stick to an embedded database and tuned sql.  Sqlite is fast enough for what amarok needs, and doesn&#039;t need a separate daemon to run it.  Mysql and Pgsql are nice, and I can see how using that if you had a shared music repository would be nice, but the same could be done by sticking the sqlite db on that same share.  sqlite has no problem with multiple processes accessing the same db.  A database running on a desktop system (unless already used for something else) would be bloat.

In my experience, unless multiple database backends is the ultimate goal the database abstraction always has to cater to the lowest common denominator, which means you have all the usefulness of a full featured rdbms like postgresql, but have to limit yourself to what sqlite can do anyway, unless your db has approximated more advanced features in the bindings proper.</description>
		<content:encoded><![CDATA[<p>Stick to an embedded database and tuned sql.  Sqlite is fast enough for what amarok needs, and doesn&#8217;t need a separate daemon to run it.  Mysql and Pgsql are nice, and I can see how using that if you had a shared music repository would be nice, but the same could be done by sticking the sqlite db on that same share.  sqlite has no problem with multiple processes accessing the same db.  A database running on a desktop system (unless already used for something else) would be bloat.</p>
<p>In my experience, unless multiple database backends is the ultimate goal the database abstraction always has to cater to the lowest common denominator, which means you have all the usefulness of a full featured rdbms like postgresql, but have to limit yourself to what sqlite can do anyway, unless your db has approximated more advanced features in the bindings proper.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Meyer</title>
		<link>http://www.sebruiz.net/162/comment-page-1#comment-922</link>
		<dc:creator>Ben Meyer</dc:creator>
		<pubDate>Fri, 15 Sep 2006 10:44:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.sebruiz.net/162#comment-922</guid>
		<description>One thing that is really cool in Qt4 is that with the modelview stuff you will be able to switch models (from a one db to another) if one database doesn&#039;t cut it while your view code wont change.

P.S. your e-mail checker doesn&#039;t allow   which is a valid e-mail char</description>
		<content:encoded><![CDATA[<p>One thing that is really cool in Qt4 is that with the modelview stuff you will be able to switch models (from a one db to another) if one database doesn&#8217;t cut it while your view code wont change.</p>
<p>P.S. your e-mail checker doesn&#8217;t allow   which is a valid e-mail char</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seb</title>
		<link>http://www.sebruiz.net/162/comment-page-1#comment-921</link>
		<dc:creator>Seb</dc:creator>
		<pubDate>Fri, 15 Sep 2006 10:41:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.sebruiz.net/162#comment-921</guid>
		<description>@Sebastián: Certainly! Using mysql or pgsql over sqlite brings speed improvements of many magnitudes - they are much faster!</description>
		<content:encoded><![CDATA[<p>@Sebastián: Certainly! Using mysql or pgsql over sqlite brings speed improvements of many magnitudes &#8211; they are much faster!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sebastián Benítez</title>
		<link>http://www.sebruiz.net/162/comment-page-1#comment-920</link>
		<dc:creator>Sebastián Benítez</dc:creator>
		<pubDate>Fri, 15 Sep 2006 10:21:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.sebruiz.net/162#comment-920</guid>
		<description>Why the need to use SQL? Why don&#039;t you use gdbm or qdbm or tdb or bdb? Even if you use SQL, having multiple backends brings choice, but are really people using other than sqlite?</description>
		<content:encoded><![CDATA[<p>Why the need to use SQL? Why don&#8217;t you use gdbm or qdbm or tdb or bdb? Even if you use SQL, having multiple backends brings choice, but are really people using other than sqlite?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: superstoned</title>
		<link>http://www.sebruiz.net/162/comment-page-1#comment-918</link>
		<dc:creator>superstoned</dc:creator>
		<pubDate>Fri, 15 Sep 2006 06:10:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.sebruiz.net/162#comment-918</guid>
		<description>wow, good morning, you should join #kat and not #strigi as #strigi isn&#039;t in use yet... ;-)</description>
		<content:encoded><![CDATA[<p>wow, good morning, you should join #kat and not #strigi as #strigi isn&#8217;t in use yet&#8230; <img src='http://www.sebruiz.net/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: superstoned</title>
		<link>http://www.sebruiz.net/162/comment-page-1#comment-917</link>
		<dc:creator>superstoned</dc:creator>
		<pubDate>Fri, 15 Sep 2006 06:09:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.sebruiz.net/162#comment-917</guid>
		<description>maybe strigi will be another option for Amarok? join #strigi on freenode &amp; ask...</description>
		<content:encoded><![CDATA[<p>maybe strigi will be another option for Amarok? join #strigi on freenode &amp; ask&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harry</title>
		<link>http://www.sebruiz.net/162/comment-page-1#comment-916</link>
		<dc:creator>Harry</dc:creator>
		<pubDate>Fri, 15 Sep 2006 05:51:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.sebruiz.net/162#comment-916</guid>
		<description>We&#039;ve used the Qt4 db classes and I must say they work perfectly. I haven&#039;t worked with the db classes in Qt3, but in 4  it is relatively easy....

Do I have wishes? Of course. Asynchronyous db stuff would be pretty cool, and of course support for more db&#039;s. But in general I&#039;m happy with it.

Even for the most simple db stuff we do with a simple sqlite db we use the Qt classes...</description>
		<content:encoded><![CDATA[<p>We&#8217;ve used the Qt4 db classes and I must say they work perfectly. I haven&#8217;t worked with the db classes in Qt3, but in 4  it is relatively easy&#8230;.</p>
<p>Do I have wishes? Of course. Asynchronyous db stuff would be pretty cool, and of course support for more db&#8217;s. But in general I&#8217;m happy with it.</p>
<p>Even for the most simple db stuff we do with a simple sqlite db we use the Qt classes&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
