<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on Anchors and links</title>
    <link>https://anchorsandlinks.com/posts/</link>
    <description>Recent content in Posts on Anchors and links</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 21 Aug 2026 20:00:00 +0100</lastBuildDate>
    <atom:link href="https://anchorsandlinks.com/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ID design and primary keys, pt. 1</title>
      <link>https://anchorsandlinks.com/posts/primary-keys/</link>
      <pubDate>Fri, 21 Aug 2026 20:00:00 +0100</pubDate>
      <guid>https://anchorsandlinks.com/posts/primary-keys/</guid>
      <description>&lt;p&gt;Author: Alexey Makhotkin &lt;a href=&#34;mailto:squadette@gmail.com&#34;&gt;squadette@gmail.com&lt;/a&gt;, &lt;em&gt;(~2300 words)&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;This is the first part of a systematic discussion of primary keys in database design. As usual, we present the material in a way that deviates from the traditional approach.&lt;/p&gt;&#xA;&lt;p&gt;This is basically a bonus chapter from the “&lt;a href=&#34;https://databasedesignbook.com/&#34;&gt;Database Design Book&lt;/a&gt;”. The goal of this text is to teach you how to design your primary keys based on business requirements.&lt;/p&gt;&#xA;&lt;p&gt;In &lt;strong&gt;part 1&lt;/strong&gt;, we begin at the logical level.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
