<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>The Name on BareSQL.com</title>
    <link>https://baresql.com/tags/the-name/</link>
    <description>Recent content in The Name on BareSQL.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 26 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://baresql.com/tags/the-name/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What the Bare in BareSQL Stands For</title>
      <link>https://baresql.com/what-the-bare-in-baresql-stands-for/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://baresql.com/what-the-bare-in-baresql-stands-for/</guid>
      <description>&lt;p&gt;BareSQL is one small program with two tools in it, and the name had to fit both. Bare does that by meaning two things at once: access laid bare, and SQL stripped down to the part every engine agrees on.&lt;/p&gt;&#xA;&lt;p&gt;The first sense belongs to BareSQL Audit. To lay something bare is to take the covers off and show what’s underneath. In a PostgreSQL database the covers are the layers between a login and a column: roles inside roles, grants made years ago to a group nobody remembers, views that read tables with their owner’s rights, functions that run as someone else. The audit takes those layers apart and lists, for each login, every column it can read and the route that gets it there.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
