<div class="gmail_quote">On Thu, Sep 15, 2011 at 12:06 PM, Stuart Morgan <span dir="ltr"><<a href="mailto:stuart@tase.co.uk">stuart@tase.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Thursday 15 Sep 2011 07:44:51 Jerry Rubinow wrote:<br>
> Would a patch be accepted which trimmed off trailing whitespace in the<br>
> channel callsigns before doing the comparison for merging channels in the<br>
> program guide?<br>
<br>
</div></div>Would it not be easier in the long term to trim the whitespace at the time the<br>
callsign is inserted into the database instead of all the places that it's<br>
read back from the database?<br>
<br>
A one-off DB update could address the existing instances of trailing/leading<br>
whitespace.<br><br></blockquote><div><br></div><div>It's always possible for a user to manually insert incorrectly terminated strings into the DB though, as frowned upon as it is to manually edit the channel table. What about doing a normalization on the callsign entries in the channel table every time mythbackend starts? </div>
<div><br></div><div>-Jerry</div></div><br>