<?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>phup &#039;n stuff &#187; PostgreSQL</title>
	<atom:link href="http://blog.kristopherwilson.com/tag/postgresql/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.kristopherwilson.com</link>
	<description>Another Blog About Being a Developer</description>
	<lastBuildDate>Tue, 31 Aug 2010 22:57:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>PostgreSQL arrays and PHP&#8217;s str_getcsv()</title>
		<link>http://blog.kristopherwilson.com/2010/03/05/postgresql-arrays-and-phps-str_getcsv/</link>
		<comments>http://blog.kristopherwilson.com/2010/03/05/postgresql-arrays-and-phps-str_getcsv/#comments</comments>
		<pubDate>Fri, 05 Mar 2010 13:28:31 +0000</pubDate>
		<dc:creator>Kristopher</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[PostgreSQL]]></category>

		<guid isPermaLink="false">http://blog.kristopherwilson.com/?p=213</guid>
		<description><![CDATA[Yesterday, while trying to figure out the best way to deal with PostgreSQL arrays in PHP, I came across the new str_getcsv() function in PHP as of 5.3. This function works much the same as fgetcsv to parse a CSV line, except that it works on a string instead of a file. For quick reference, [...]]]></description>
		<wfw:commentRss>http://blog.kristopherwilson.com/2010/03/05/postgresql-arrays-and-phps-str_getcsv/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>array_to_string in PostgreSQL</title>
		<link>http://blog.kristopherwilson.com/2010/02/17/array-to-string-in-postgresql/</link>
		<comments>http://blog.kristopherwilson.com/2010/02/17/array-to-string-in-postgresql/#comments</comments>
		<pubDate>Wed, 17 Feb 2010 14:06:12 +0000</pubDate>
		<dc:creator>Kristopher</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[PostgreSQL]]></category>

		<guid isPermaLink="false">http://www.kristopherwilson.com/?p=169</guid>
		<description><![CDATA[This snippet courtesy of Kieran Smith. Want to get more work done in a single query? Tired of looping through query results to simply build a list of data. How about this? SELECT array_to_string&#40; ARRAY&#40; SELECT name FROM projects WHERE customer_id = 10 ORDER BY LOWER&#40;name&#41; &#41;, ', ' &#41; AS projects; What you are [...]]]></description>
		<wfw:commentRss>http://blog.kristopherwilson.com/2010/02/17/array-to-string-in-postgresql/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Automatically Setting Modified Date Database Fields</title>
		<link>http://blog.kristopherwilson.com/2010/01/19/automatically-setting-modified-date-database-fields/</link>
		<comments>http://blog.kristopherwilson.com/2010/01/19/automatically-setting-modified-date-database-fields/#comments</comments>
		<pubDate>Tue, 19 Jan 2010 18:04:39 +0000</pubDate>
		<dc:creator>Kristopher</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[PostgreSQL]]></category>

		<guid isPermaLink="false">http://www.kristopherwilson.com/?p=135</guid>
		<description><![CDATA[Most of my database tables have a <code>last_modified_on</code> column that is populated with the data the a record was last updated. The problem is, we can't set a default of the current date and time on this column, because it would be populated on create. Of course, we could handle this in code, but this is something I like leaving up to the database. 

Here's how I do it.]]></description>
		<wfw:commentRss>http://blog.kristopherwilson.com/2010/01/19/automatically-setting-modified-date-database-fields/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>PostgreSQL 8.4.2-r1 on Gentoo</title>
		<link>http://blog.kristopherwilson.com/2010/01/08/postgres-8-4-2-r1-on-gentoo/</link>
		<comments>http://blog.kristopherwilson.com/2010/01/08/postgres-8-4-2-r1-on-gentoo/#comments</comments>
		<pubDate>Sat, 09 Jan 2010 00:53:14 +0000</pubDate>
		<dc:creator>Kristopher</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[PostgreSQL]]></category>

		<guid isPermaLink="false">http://www.kristopherwilson.com/?p=106</guid>
		<description><![CDATA[A new version of PostgreSQL, 8.4.2-r1, is available in Gentoo Portage, but be careful. It appears the server is compiled with HAVE_INT64_TIMESTAMP by default, something not true with previous versions. Because of this, after updating, you might get an error about the data cluster being incompatibile with the server when you restart, unless you were [...]]]></description>
		<wfw:commentRss>http://blog.kristopherwilson.com/2010/01/08/postgres-8-4-2-r1-on-gentoo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Inheritance in PostgreSQL</title>
		<link>http://blog.kristopherwilson.com/2010/01/01/inheritance-in-postgresql/</link>
		<comments>http://blog.kristopherwilson.com/2010/01/01/inheritance-in-postgresql/#comments</comments>
		<pubDate>Sat, 02 Jan 2010 03:33:04 +0000</pubDate>
		<dc:creator>Kristopher</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[PostgreSQL]]></category>

		<guid isPermaLink="false">http://www.kristopherwilson.com/?p=99</guid>
		<description><![CDATA[Another cool feature I've recently discovered in PostgreSQL, although one available and documented for a long time, is table inheritance, which works almost exactly like object inheritance in object oriented programming. This simply means that you can have tables inheriting columns from parent tables. 

And it's extremely easy to implement.]]></description>
		<wfw:commentRss>http://blog.kristopherwilson.com/2010/01/01/inheritance-in-postgresql/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Returning in PostgreSQL</title>
		<link>http://blog.kristopherwilson.com/2009/11/20/returning-in-postgresql/</link>
		<comments>http://blog.kristopherwilson.com/2009/11/20/returning-in-postgresql/#comments</comments>
		<pubDate>Sat, 21 Nov 2009 01:13:32 +0000</pubDate>
		<dc:creator>Kristopher</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[PostgreSQL]]></category>

		<guid isPermaLink="false">http://www.kristopherwilson.com/?p=79</guid>
		<description><![CDATA[I recently came across an amazing feature in PostgreSQL: the RETURNING clause. This clause allows you to return specific data as the result of an INSERT or UPDATE query. Often, after doing one of these queries, I&#8217;m interested in getting some data, such as an autogenerated primary key field, or maybe some defaulted data (like [...]]]></description>
		<wfw:commentRss>http://blog.kristopherwilson.com/2009/11/20/returning-in-postgresql/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>PostgreSQL 8.3 Permissions in Gentoo</title>
		<link>http://blog.kristopherwilson.com/2009/03/07/postgresql-83-permissions-in-gentoo/</link>
		<comments>http://blog.kristopherwilson.com/2009/03/07/postgresql-83-permissions-in-gentoo/#comments</comments>
		<pubDate>Sat, 07 Mar 2009 17:44:55 +0000</pubDate>
		<dc:creator>Kristopher</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[PostgreSQL]]></category>

		<guid isPermaLink="false">http://www.kristopherwilson.com/?p=44</guid>
		<description><![CDATA[PostgreSQL 8.3 in Gentoo now creates the socket in /var/run/postgresql with stricter permissions, meaning that regular users cannot connect to the PostgreSQL server via command line. Emerging this package outputs a message about this that I initially missed when installing: Please note that the standard location of the socket has changed from /tmp to /var/run/postgresql [...]]]></description>
		<wfw:commentRss>http://blog.kristopherwilson.com/2009/03/07/postgresql-83-permissions-in-gentoo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Upgrading to PostgreSQL 8.3 on Gentoo</title>
		<link>http://blog.kristopherwilson.com/2009/03/04/upgrading-to-postgresql-83-on-gentoo/</link>
		<comments>http://blog.kristopherwilson.com/2009/03/04/upgrading-to-postgresql-83-on-gentoo/#comments</comments>
		<pubDate>Thu, 05 Mar 2009 03:45:36 +0000</pubDate>
		<dc:creator>Kristopher</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[PostgreSQL]]></category>

		<guid isPermaLink="false">http://www.kristopherwilson.com/?p=37</guid>
		<description><![CDATA[Gentoo has taken a long time to unmask PostgreSQL 8.3 in Portage. Currently, the best version you can get is. 8.0.5, which, if you can tell, is pretty far away from 8.3. 

This masking is largely due to the painful process of upgrading PostgreSQL (which usually involves dumping all your databases and restoring them afterwards). Here's what I did to get 8.3 up and running.]]></description>
		<wfw:commentRss>http://blog.kristopherwilson.com/2009/03/04/upgrading-to-postgresql-83-on-gentoo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
