<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SQL on GBIF Data Blog</title>
    <link>https://data-blog.gbif.org/tags/sql/</link>
    <description>Recent content in SQL on GBIF Data Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 14 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://data-blog.gbif.org/tags/sql/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Recent breaking changes to SQL downloads to support the COL XR</title>
      <link>https://data-blog.gbif.org/post/sql-downloads-col-xr/</link>
      <pubDate>Wed, 14 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://data-blog.gbif.org/post/sql-downloads-col-xr/</guid>
      <description>&lt;p&gt;GBIF SQL downloads now use the &lt;a href=&#34;https://www.catalogueoflife.org/building/releases&#34;&gt;Catalogue of Life Extended Release (COL XR)&lt;/a&gt; as the default taxonomy for organizing results. They also use COL XR taxon keys by default. &lt;a href=&#34;https://data-blog.gbif.org/post/catalogue-of-life-taxonomic-backbone/&#34;&gt;See the previous post for more information.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;If you have existing SQL queries that use numeric GBIF Backbone taxon keys, update them to use alphanumeric COL XR keys or reference the &lt;code&gt;gbif_classification&lt;/code&gt; field to continue using the GBIF Backbone taxonomy. Because the GBIF Backbone will not be updated, we recommend transitioning your queries and scripts to COL XR.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
