<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.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: Category postgresql</title>
    <link>http://blog.melhase.net/articles/category/postgresql</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>enough water makes all rocks round</description>
    <item>
      <title>Automatic Pickle Serialization and Deserialization with PostgreSQL</title>
      <description>&lt;p&gt;Building on the earlier success of creating a pickle data type in PostgreSQL, I've come up with this small and comfortable way of automatically serializing and de-serializing python pickles with PostgreSQL and psycopg2.&lt;/p&gt;</description>
      <pubDate>Tue, 13 Jun 2006 00:00:00 -0400</pubDate>
      <guid isPermaLink="false">urn:uuid:f1936f81-9ab0-43bf-9ddd-4ad99ff4e17c</guid>
      <author>troy</author>
      <link>http://blog.melhase.net/articles/2006/06/13/auto-postgresql-pickles</link>
      <category>python</category>
      <category>postgresql</category>
      <trackback:ping>http://blog.melhase.net/articles/trackback/9</trackback:ping>
    </item>
    <item>
      <title>SELECT Surprise</title>
      <description>&lt;p&gt;While experimenting with unicode values in Python, PostgreSQL and pyscopg2, I ran a little query like this:&lt;/p&gt;

&lt;div class="typocode"&gt;&lt;pre&gt;&lt;code class="typocode_python "&gt;&amp;gt;&amp;gt;&amp;gt; cur.execute(&amp;quot;SELECT (note_id, body) FROM troy.morenotes&amp;quot;)
&amp;gt;&amp;gt;&amp;gt; cur.fetchall()
[('(1,&amp;quot;The rain in Spain falls mainly in the plains.&amp;quot;)',),
 ('(2,&amp;quot;Twenty dwarves did handstands on the carpet.&amp;quot;)',),
 ('(5,I\xc3\xb1t\xc3\xabrn\xc3\xa2ti\xc3\xb4n\xc3\xa0liz\xc3\xa6ti\xc3\xb8n)',)]&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;</description>
      <pubDate>Tue, 13 Jun 2006 00:00:00 -0400</pubDate>
      <guid isPermaLink="false">urn:uuid:3337424b-481d-4d65-b1b4-5e1f581cd119</guid>
      <author>troy</author>
      <link>http://blog.melhase.net/articles/2006/06/13/select-surprise</link>
      <category>python</category>
      <category>postgresql</category>
      <trackback:ping>http://blog.melhase.net/articles/trackback/5</trackback:ping>
    </item>
    <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>
