<?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 on: PostgreSQL UUIDs and ColdFusion (2)</title>
	<atom:link href="http://jochem.vandieten.net/2008/02/10/postgresql-uuids-and-coldfusion-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://jochem.vandieten.net/2008/02/10/postgresql-uuids-and-coldfusion-2/</link>
	<description>Jochem's tech exploits</description>
	<pubDate>Wed, 10 Jun 2026 14:44:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Brian</title>
		<link>http://jochem.vandieten.net/2008/02/10/postgresql-uuids-and-coldfusion-2/comment-page-1/#comment-122</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Tue, 16 Dec 2008 05:49:33 +0000</pubDate>
		<guid isPermaLink="false">http://jochem.vandieten.net/2008/02/10/postgresql-uuids-and-coldfusion-2/#comment-122</guid>
		<description>Interesting idea to just skip to GUIDs.  I guess that has better universal support minus the createUUID() function.  Converting an existing database to GUIDs might be a semi-PITA if using them as primary/foreign keys.  Food for thought, thanks Jochem!

ps - not having a "subscribe to comments" option on the blog is annoying... no way to know if you or anyone else replies!</description>
		<content:encoded><![CDATA[<p>Interesting idea to just skip to GUIDs.  I guess that has better universal support minus the createUUID() function.  Converting an existing database to GUIDs might be a semi-PITA if using them as primary/foreign keys.  Food for thought, thanks Jochem!</p>
<p>ps - not having a &#8220;subscribe to comments&#8221; option on the blog is annoying&#8230; no way to know if you or anyone else replies!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jochem</title>
		<link>http://jochem.vandieten.net/2008/02/10/postgresql-uuids-and-coldfusion-2/comment-page-1/#comment-109</link>
		<dc:creator>Jochem</dc:creator>
		<pubDate>Thu, 11 Dec 2008 21:09:41 +0000</pubDate>
		<guid isPermaLink="false">http://jochem.vandieten.net/2008/02/10/postgresql-uuids-and-coldfusion-2/#comment-109</guid>
		<description>I don't think it is currently possible without patching either PostgreSQL or the JDBC driver.

It is on my list of things to figure out once the PostgreSQL 8.4 beta is out. The patch to make PostgreSQL understand ColdFusion UUIDs &lt;a href="http://archives.postgresql.org/pgsql-committers/2008-11/msg00020.php" rel="nofollow"&gt;was committed last month&lt;/a&gt; so at least one side of the equation has gotten easier. The other side is something that Adobe has to fix, hopefully for the ColdFusion 9 timeframe. But I am more and more inclined to just abandon all ColdFusion UUID crap and switch everything to the standard format (which in ColdFusion is known as GUID).</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think it is currently possible without patching either PostgreSQL or the JDBC driver.</p>
<p>It is on my list of things to figure out once the PostgreSQL 8.4 beta is out. The patch to make PostgreSQL understand ColdFusion UUIDs <a href="http://archives.postgresql.org/pgsql-committers/2008-11/msg00020.php" rel="nofollow">was committed last month</a> so at least one side of the equation has gotten easier. The other side is something that Adobe has to fix, hopefully for the ColdFusion 9 timeframe. But I am more and more inclined to just abandon all ColdFusion UUID crap and switch everything to the standard format (which in ColdFusion is known as GUID).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://jochem.vandieten.net/2008/02/10/postgresql-uuids-and-coldfusion-2/comment-page-1/#comment-108</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Thu, 11 Dec 2008 20:52:59 +0000</pubDate>
		<guid isPermaLink="false">http://jochem.vandieten.net/2008/02/10/postgresql-uuids-and-coldfusion-2/#comment-108</guid>
		<description>Jochem, 

Forgive the would-be-newbie PG question - I have not worked with new datatypes previously.  Is it possible to get this functionality without recompiling postgres?  I've seen this approach before:  http://code.google.com/p/polarrose-postgresql-uuid/source/browse/

But don't know how it changes now that the uuid type is built-in?  I manage my postgres with yum on CentOS so I would like to avoid recompiling if at all possible.

Thanks!

Brian</description>
		<content:encoded><![CDATA[<p>Jochem, </p>
<p>Forgive the would-be-newbie PG question - I have not worked with new datatypes previously.  Is it possible to get this functionality without recompiling postgres?  I&#8217;ve seen this approach before:  <a href="http://code.google.com/p/polarrose-postgresql-uuid/source/browse/" rel="nofollow">http://code.google.com/p/polarrose-postgresql-uuid/source/browse/</a></p>
<p>But don&#8217;t know how it changes now that the uuid type is built-in?  I manage my postgres with yum on CentOS so I would like to avoid recompiling if at all possible.</p>
<p>Thanks!</p>
<p>Brian</p>
]]></content:encoded>
	</item>
</channel>
</rss>
