<?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 for rwec.co.uk</title>
	<atom:link href="http://rwec.co.uk/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://rwec.co.uk/blog</link>
	<description>Rowan&#039;s World, Et Cetera</description>
	<lastBuildDate>Wed, 16 May 2012 12:34:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>Comment on Atomic Translations &#8211; Part 2 &#8211; Translated Text as a Data Type in PostgreSQL by Rowan</title>
		<link>http://rwec.co.uk/blog/2009/12/atomic-translations-part-2/comment-page-1/#comment-30661</link>
		<dc:creator>Rowan</dc:creator>
		<pubDate>Wed, 16 May 2012 12:34:05 +0000</pubDate>
		<guid isPermaLink="false">http://rwec.co.uk/blog/?p=60#comment-30661</guid>
		<description>Easy! :) A WHERE clause can have all the same syntax as a SELECT clause, so you just query against whichever translation you want:

SELECT * FROM &quot;countries&quot; WHERE &quot;name&quot;-&gt;&#039;en&#039; LIKE &#039;Ger%&#039;

It does mean the function is being run on every column in the table, so there are performance considerations, but that&#039;s true of most of the schemas I&#039;ve seen for translating this kind of data (One Big Table, tables where you previously had columns, etc, all lead to much more complex query plans).

I haven&#039;t looked into it in detail, but I think you could build an index on (&quot;name&quot;-&gt;&#039;en&#039;) if you knew that you were going to query it in a way that would hit the index. Although if you were doing pattern matching, that might not help anyway...

Meanwhile, I must get round to updating the version online with the fixes that have been made to get it working in production here.</description>
		<content:encoded><![CDATA[<p>Easy! :) A WHERE clause can have all the same syntax as a SELECT clause, so you just query against whichever translation you want:</p>
<p>SELECT * FROM "countries" WHERE "name"->'en' LIKE 'Ger%'</p>
<p>It does mean the function is being run on every column in the table, so there are performance considerations, but that's true of most of the schemas I've seen for translating this kind of data (One Big Table, tables where you previously had columns, etc, all lead to much more complex query plans).</p>
<p>I haven't looked into it in detail, but I think you could build an index on ("name"->'en') if you knew that you were going to query it in a way that would hit the index. Although if you were doing pattern matching, that might not help anyway...</p>
<p>Meanwhile, I must get round to updating the version online with the fixes that have been made to get it working in production here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Atomic Translations &#8211; Part 2 &#8211; Translated Text as a Data Type in PostgreSQL by Taai</title>
		<link>http://rwec.co.uk/blog/2009/12/atomic-translations-part-2/comment-page-1/#comment-30658</link>
		<dc:creator>Taai</dc:creator>
		<pubDate>Wed, 16 May 2012 11:50:23 +0000</pubDate>
		<guid isPermaLink="false">http://rwec.co.uk/blog/?p=60#comment-30658</guid>
		<description>Very interesting and useful. But how to do a search, for example, SELECT * FROM &quot;countries&quot; WHERE &quot;name&quot; LIKE &#039;Ger%&#039; ?</description>
		<content:encoded><![CDATA[<p>Very interesting and useful. But how to do a search, for example, SELECT * FROM "countries" WHERE "name" LIKE 'Ger%' ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on iCalendar for English Bank Holidays by Rowan</title>
		<link>http://rwec.co.uk/blog/2009/08/icalendar-for-english-bank-holidays/comment-page-1/#comment-29524</link>
		<dc:creator>Rowan</dc:creator>
		<pubDate>Wed, 25 Apr 2012 08:21:14 +0000</pubDate>
		<guid isPermaLink="false">http://rwec.co.uk/blog/?p=32#comment-29524</guid>
		<description>Hi Jon,

The calendar currently includes all the Bank Holidays up to the end of 2012; it looks like the government site lists the &quot;expected&quot; dates up to 2015 now, though, so I will update with those shortly. :)</description>
		<content:encoded><![CDATA[<p>Hi Jon,</p>
<p>The calendar currently includes all the Bank Holidays up to the end of 2012; it looks like the government site lists the "expected" dates up to 2015 now, though, so I will update with those shortly. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on iCalendar for English Bank Holidays by Jon</title>
		<link>http://rwec.co.uk/blog/2009/08/icalendar-for-english-bank-holidays/comment-page-1/#comment-29494</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Tue, 24 Apr 2012 21:19:58 +0000</pubDate>
		<guid isPermaLink="false">http://rwec.co.uk/blog/?p=32#comment-29494</guid>
		<description>Any chance of updating for 2012 / 2013. I have only just seen this site!</description>
		<content:encoded><![CDATA[<p>Any chance of updating for 2012 / 2013. I have only just seen this site!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Daylight Savings Time: a White Lie, or a Waste of Time? by Rowan</title>
		<link>http://rwec.co.uk/blog/2010/04/daylight-savings-time-waste/comment-page-1/#comment-28128</link>
		<dc:creator>Rowan</dc:creator>
		<pubDate>Sun, 25 Mar 2012 11:02:50 +0000</pubDate>
		<guid isPermaLink="false">http://rwec.co.uk/blog/?p=105#comment-28128</guid>
		<description>The question is not so much whether we could make better use of available daylight, but whether the best way to do that is by tricking everyone into thinking they&#039;re getting up at the same time when they&#039;re not. If you don&#039;t think there&#039;s any other way of doing it, fair enough, but don&#039;t pretend it&#039;s anything other than a cheap lie. Personally I think in the 21st century we can come up with a better solution. See http://camtim.org.uk for more.</description>
		<content:encoded><![CDATA[<p>The question is not so much whether we could make better use of available daylight, but whether the best way to do that is by tricking everyone into thinking they're getting up at the same time when they're not. If you don't think there's any other way of doing it, fair enough, but don't pretend it's anything other than a cheap lie. Personally I think in the 21st century we can come up with a better solution. See <a href="http://camtim.org.uk" rel="nofollow">http://camtim.org.uk</a> for more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Daylight Savings Time: a White Lie, or a Waste of Time? by Alex</title>
		<link>http://rwec.co.uk/blog/2010/04/daylight-savings-time-waste/comment-page-1/#comment-28077</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Sat, 24 Mar 2012 13:10:16 +0000</pubDate>
		<guid isPermaLink="false">http://rwec.co.uk/blog/?p=105#comment-28077</guid>
		<description>Great opinion, but I disagree.  I don&#039;t think Britain needs to live in darkness. That is because while just about everyone is up in the evening, only a portion of the population is up at sunrise. So the morning light is wasted. Also, the studies showing fewer fatalities and reduced energy use with later daylight are all true, these studies have been clearly replicated across many countries. Britian should adopt the European time zone, it&#039;s the simpler and smarter solution.</description>
		<content:encoded><![CDATA[<p>Great opinion, but I disagree.  I don't think Britain needs to live in darkness. That is because while just about everyone is up in the evening, only a portion of the population is up at sunrise. So the morning light is wasted. Also, the studies showing fewer fatalities and reduced energy use with later daylight are all true, these studies have been clearly replicated across many countries. Britian should adopt the European time zone, it's the simpler and smarter solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cached Redirects Considered Harmful (and how browsers can fix them) by Mike</title>
		<link>http://rwec.co.uk/blog/2011/10/cached-redirects-considered-harmful/comment-page-1/#comment-22564</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Thu, 22 Dec 2011 21:08:36 +0000</pubDate>
		<guid isPermaLink="false">http://rwec.co.uk/blog/?p=200#comment-22564</guid>
		<description>For those of you who use mod_rewrite I&#039;ve found a great workaround!  (works for me).

http://mark.koli.ch/2010/12/set-cache-control-and-expires-headers-on-a-redirect-with-mod-rewrite.html

Yeah!  Of course this doesn&#039;t fix existing problems, but at least moving forward I&#039;ve found a new best practice that I&#039;ll be following.</description>
		<content:encoded><![CDATA[<p>For those of you who use mod_rewrite I've found a great workaround!  (works for me).</p>
<p><a href="http://mark.koli.ch/2010/12/set-cache-control-and-expires-headers-on-a-redirect-with-mod-rewrite.html" rel="nofollow">http://mark.koli.ch/2010/12/set-cache-control-and-expires-headers-on-a-redirect-with-mod-rewrite.html</a></p>
<p>Yeah!  Of course this doesn't fix existing problems, but at least moving forward I've found a new best practice that I'll be following.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cached Redirects Considered Harmful (and how browsers can fix them) by Mike</title>
		<link>http://rwec.co.uk/blog/2011/10/cached-redirects-considered-harmful/comment-page-1/#comment-22563</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Thu, 22 Dec 2011 20:23:22 +0000</pubDate>
		<guid isPermaLink="false">http://rwec.co.uk/blog/?p=200#comment-22563</guid>
		<description>I&#039;m with Rowan and Dominick on this.  I&#039;m not following harry&#039;s argument.  Dominick&#039;s assertion makes perfect sense.</description>
		<content:encoded><![CDATA[<p>I'm with Rowan and Dominick on this.  I'm not following harry's argument.  Dominick's assertion makes perfect sense.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cached Redirects Considered Harmful (and how browsers can fix them) by Rowan</title>
		<link>http://rwec.co.uk/blog/2011/10/cached-redirects-considered-harmful/comment-page-1/#comment-22114</link>
		<dc:creator>Rowan</dc:creator>
		<pubDate>Thu, 15 Dec 2011 15:19:43 +0000</pubDate>
		<guid isPermaLink="false">http://rwec.co.uk/blog/?p=200#comment-22114</guid>
		<description>I don&#039;t follow. Why would it be OK for the owner of tinyurl.com (the domain of the shortened URL) to lose control of that redirect (the asset in question)? The owner of the target domain doesn&#039;t have any more control of the incoming redirect than any other inbound link.

And given that the mnemonic in the spec is &quot;Moved Permanently&quot;, I don&#039;t think URL shortening was &quot;the reason that 301 was created&quot;. 

I believe some URL shorteners also allow editing of the redirect, so would need to be careful of cache control!</description>
		<content:encoded><![CDATA[<p>I don't follow. Why would it be OK for the owner of tinyurl.com (the domain of the shortened URL) to lose control of that redirect (the asset in question)? The owner of the target domain doesn't have any more control of the incoming redirect than any other inbound link.</p>
<p>And given that the mnemonic in the spec is "Moved Permanently", I don't think URL shortening was "the reason that 301 was created". </p>
<p>I believe some URL shorteners also allow editing of the redirect, so would need to be careful of cache control!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cached Redirects Considered Harmful (and how browsers can fix them) by harry</title>
		<link>http://rwec.co.uk/blog/2011/10/cached-redirects-considered-harmful/comment-page-1/#comment-22113</link>
		<dc:creator>harry</dc:creator>
		<pubDate>Thu, 15 Dec 2011 15:13:46 +0000</pubDate>
		<guid isPermaLink="false">http://rwec.co.uk/blog/?p=200#comment-22113</guid>
		<description>&gt; &quot;There is no logical reason - EVER - to make it so that the owner of a domain no longer has control of an asset&quot;
what a load of rubbish, what about url shorteners, these are exactly the reason that 301 created and shows developers using it properly.</description>
		<content:encoded><![CDATA[<p>&gt; "There is no logical reason - EVER - to make it so that the owner of a domain no longer has control of an asset"<br />
what a load of rubbish, what about url shorteners, these are exactly the reason that 301 created and shows developers using it properly.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

