<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>rwec.co.uk &#187; postresql</title>
	<atom:link href="http://rwec.co.uk/blog/tag/postresql/feed/" rel="self" type="application/rss+xml" />
	<link>http://rwec.co.uk/blog</link>
	<description>Rowan&#039;s World, Et Cetera</description>
	<lastBuildDate>Mon, 06 Sep 2010 12:53:27 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Atomic Translations &#8211; Part 2 &#8211; Translated Text as a Data Type in PostgreSQL</title>
		<link>http://rwec.co.uk/blog/2009/12/atomic-translations-part-2/</link>
		<comments>http://rwec.co.uk/blog/2009/12/atomic-translations-part-2/#comments</comments>
		<pubDate>Sat, 12 Dec 2009 23:42:37 +0000</pubDate>
		<dc:creator>Rowan</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[atomicity]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[i18n]]></category>
		<category><![CDATA[internationalization]]></category>
		<category><![CDATA[library]]></category>
		<category><![CDATA[postgres]]></category>
		<category><![CDATA[postresql]]></category>
		<category><![CDATA[projects]]></category>
		<category><![CDATA[prototype]]></category>

		<guid isPermaLink="false">http://rwec.co.uk/blog/?p=60</guid>
		<description><![CDATA[[Part 1: Database i18n as a Data Type Problem &#124; Prototype Postgres Library] In my last post (longer ago than I intended), I discussed the approaches I&#8217;ve come across to adding i18n to a database schema, and outlined my theory that the whole problem could be recast as one of data types. In order to [...]]]></description>
		<wfw:commentRss>http://rwec.co.uk/blog/2009/12/atomic-translations-part-2/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Atomic Translations &#8211; Part 1 &#8211; Database i18n as a Data Type Problem</title>
		<link>http://rwec.co.uk/blog/2009/11/atomic-translations-part-1/</link>
		<comments>http://rwec.co.uk/blog/2009/11/atomic-translations-part-1/#comments</comments>
		<pubDate>Mon, 23 Nov 2009 00:10:18 +0000</pubDate>
		<dc:creator>Rowan</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[atomicity]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[i18n]]></category>
		<category><![CDATA[internationalization]]></category>
		<category><![CDATA[postgres]]></category>
		<category><![CDATA[postresql]]></category>

		<guid isPermaLink="false">http://rwec.co.uk/blog/?p=50</guid>
		<description><![CDATA[[Part 2: Translated Text as a Data Type in PostgreSQL &#124; Prototype Postgres Library] The most obvious task when making any application multi-lingual is to make the UI translatable; there are absolutely tons of options for this, libraries in all sorts of languages, recipes, discussions, etc. But for many applications there&#8217;s another task, just as [...]]]></description>
		<wfw:commentRss>http://rwec.co.uk/blog/2009/11/atomic-translations-part-1/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
