<?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 8.3: UUID, XML, ENUMs&#8230;</title>
	<atom:link href="http://www.ghidinelli.com/2008/02/04/postgresql-83-uuid-xml-enums/feed" rel="self" type="application/rss+xml" />
	<link>http://www.ghidinelli.com/2008/02/04/postgresql-83-uuid-xml-enums</link>
	<description></description>
	<lastBuildDate>Thu, 01 Jun 2017 18:51:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jochem van Dieten</title>
		<link>http://www.ghidinelli.com/2008/02/04/postgresql-83-uuid-xml-enums/comment-page-1#comment-43911</link>
		<dc:creator>Jochem van Dieten</dc:creator>
		<pubDate>Wed, 06 Feb 2008 11:29:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.ghidinelli.com/2008/02/04/postgresql-83-uuid-xml-enums/#comment-43911</guid>
		<description>The &lt;a href=&quot;http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/uuid.c?rev=1.7;content-type=text%2Fx-cvsweb-markup&quot; rel=&quot;nofollow&quot;&gt;PostgreSQL impelmentation&lt;/a&gt; is to remove all hyphens, convert the resulting 32 hex characters to a 16-byte string and use that string internally. Only when outputted to a front-end it is converted back to a 36-byte string.</description>
		<content:encoded><![CDATA[<p>The <a href="http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/uuid.c?rev=1.7;content-type=text%2Fx-cvsweb-markup" rel="nofollow">PostgreSQL impelmentation</a> is to remove all hyphens, convert the resulting 32 hex characters to a 16-byte string and use that string internally. Only when outputted to a front-end it is converted back to a 36-byte string.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brian</title>
		<link>http://www.ghidinelli.com/2008/02/04/postgresql-83-uuid-xml-enums/comment-page-1#comment-43886</link>
		<dc:creator>brian</dc:creator>
		<pubDate>Tue, 05 Feb 2008 17:37:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.ghidinelli.com/2008/02/04/postgresql-83-uuid-xml-enums/#comment-43886</guid>
		<description>MSSQL does have a &quot;uniqueidentifier&quot; type which is a GUID storage bin that does something numeric or bit behind the scenes.  I&#039;m guessing that Postgres&#039; implementation is similar.

It&#039;s interesting there still isn&#039;t a createGUID() function in ColdFusion since you can check isValid(&quot;guid&quot;, value).  Check but not create?  Kind of silly.  The livedocs even point to your function on cflib.org!</description>
		<content:encoded><![CDATA[<p>MSSQL does have a &#8220;uniqueidentifier&#8221; type which is a GUID storage bin that does something numeric or bit behind the scenes.  I&#8217;m guessing that Postgres&#8217; implementation is similar.</p>
<p>It&#8217;s interesting there still isn&#8217;t a createGUID() function in ColdFusion since you can check isValid(&#8220;guid&#8221;, value).  Check but not create?  Kind of silly.  The livedocs even point to your function on cflib.org!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan D</title>
		<link>http://www.ghidinelli.com/2008/02/04/postgresql-83-uuid-xml-enums/comment-page-1#comment-43866</link>
		<dc:creator>Nathan D</dc:creator>
		<pubDate>Mon, 04 Feb 2008 21:53:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.ghidinelli.com/2008/02/04/postgresql-83-uuid-xml-enums/#comment-43866</guid>
		<description>I have not looked at all at this version of PostgreSQL, but I seem to recall back in the day there were reasons to use the 36-char ID with MS SQL Server due to the way the underlying engine dealt with the indexing -- something about storing it in some more efficient form than a char(35) (and my lack of specific knowledge on this is a clear sign I ought not be posting this suggestion).

And since I was literally shocked to find out how long ago I wrote this function, I will give the obligatory link to the (silly simple) createGUID function on CFLib: http://www.cflib.org/udf.cfm?ID=54</description>
		<content:encoded><![CDATA[<p>I have not looked at all at this version of PostgreSQL, but I seem to recall back in the day there were reasons to use the 36-char ID with MS SQL Server due to the way the underlying engine dealt with the indexing &#8212; something about storing it in some more efficient form than a char(35) (and my lack of specific knowledge on this is a clear sign I ought not be posting this suggestion).</p>
<p>And since I was literally shocked to find out how long ago I wrote this function, I will give the obligatory link to the (silly simple) createGUID function on CFLib: <a href="http://www.cflib.org/udf.cfm?ID=54" rel="nofollow">http://www.cflib.org/udf.cfm?ID=54</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
