<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/stylesheets/rss.css" type="text/css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Round Rock River: A Tale of PostgreSQL Types and Python</title>
    <link>http://blog.melhase.net/articles/2006/06/06/a-tale-of-postgresql-types-and-python</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>enough water makes all rocks round</description>
    <item>
      <title>A Tale of PostgreSQL Types and Python</title>
      <description>&lt;p&gt;Thinking of integrating user-defined types in PostgreSQL and psycopg2? Here's the path I walked, hopefully you can avoid the same pitfalls.&lt;/p&gt;

&lt;p&gt;I was after a PostgreSQL data type for storing Python pickles. This seemed simple enough because the database facility for aliasing a type already exists. So the first thing I tried was a CREATE DOMAIN statement in PG, like so:&lt;/p&gt;</description>
      <pubDate>Tue, 06 Jun 2006 00:00:00 -0400</pubDate>
      <guid isPermaLink="false">urn:uuid:3bf2586d-2394-4be0-abbe-d063c48aee47</guid>
      <author>troy</author>
      <link>http://blog.melhase.net/articles/2006/06/06/a-tale-of-postgresql-types-and-python</link>
      <category>python</category>
      <category>postgresql</category>
      <trackback:ping>http://blog.melhase.net/articles/trackback/4</trackback:ping>
    </item>
  </channel>
</rss>
