<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Identifiers on Nalar</title>
    <link>https://nalar.dev/tags/identifiers/</link>
    <description>Recent content in Identifiers on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/identifiers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Migrate Time-Based Identifiers from UUIDv1 to UUIDv6 in Python 3.14</title>
      <link>https://nalar.dev/migrate-time-based-identifiers-from-uuid1-to-uuid6/</link>
      <pubDate>Wed, 09 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/migrate-time-based-identifiers-from-uuid1-to-uuid6/</guid>
      <description>&lt;p&gt;UUID version 1 has been around for a long time. It combines a timestamp, a clock sequence, and a node identifier into a 128-bit value, which makes it useful when applications need identifiers that can be generated without coordinating through a central database sequence.&lt;/p&gt;&#xA;&lt;p&gt;Its layout has an awkward property, though: the timestamp bits are not arranged from most significant to least significant in the same order that ordinary UUID comparison uses.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
