Strange.<br><br>I've run postgres with Amarok exclusively for ages and haven't seen any such bugs. But... since I don't use podcasts much, I'll test this and get back to you.<br> <br>Peter<br><br><div><span class="gmail_quote">
On 06/11/2007, <b class="gmail_sendername">Seb Ruiz</b> <<a href="mailto:ruiz@kde.org">ruiz@kde.org</a>> wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex">
Hi All,<br>There is a rather serious bug with the postgres backend which makes<br>all boolean values to be incorrectly read from the database. Case in<br>point is saving "auto transfer" or "purge" properties from podcast
<br>channel settings. I have established that the correct boolean entry is<br>written to the database, but our code is always returning false.<br><br>If you look at this code:<br><br>pcb.setAutoScan( *++it == boolT() ? true : false );
<br><br>Where *++it is the iterator pointing to a QString which is the result<br>returned from the database.<br><br>boolT() returns "true" for postgres connections, however the database<br>will return "t" as an indicator for a true boolean. The converse is
<br>not a problem since psql accepts any sort of 'truthy' value as input<br>(eg, 1, true, t, y).<br><br>I do not know if psql < 8 return "t" or "true" - this is my only<br>concern. Except, that most distros will ship psql
8.1/8.2.<br><br>I am not actually running psql so I cannot test it, it is simply a<br>theory which I am confident that I am correct with.<br><br>Thoughts please.<br><br><br>--<br>Seb Ruiz<br><br><a href="http://www.sebruiz.net/">
http://www.sebruiz.net/</a><br></blockquote></div><br><br clear="all"><br>-- <br>"Happiness makes up in height what it lacks in length"<br>-- Robert Frost