<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>BareSQL on BareSQL.com</title>
    <link>https://baresql.com/tags/baresql/</link>
    <description>Recent content in BareSQL 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/baresql/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>BareSQL Launches With an Access Audit for PostgreSQL and a Portability Check for SQL</title>
      <link>https://baresql.com/baresql-launches-with-an-access-audit-for-postgresql-and-a-portability-check-for-sql/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://baresql.com/baresql-launches-with-an-access-audit-for-postgresql-and-a-portability-check-for-sql/</guid>
      <description>&lt;p&gt;BareSQL is a free, open-source command-line program with two tools in it. BareSQL Audit lists every column each PostgreSQL login can read, with the route that gets it there, and marks the ones that hold personal data. BareSQL Portable finds the SQL that fails or answers differently on SQLite, PostgreSQL, MySQL and MariaDB. Version 0.1.0 is the first release.&lt;/p&gt;&#xA;&lt;p&gt;Who can read the customers&amp;rsquo; email addresses? In a PostgreSQL database the answer is spread over role memberships, grants made years ago, views that read tables with their owner’s rights, default privileges and row security policies. Working it out by hand means an afternoon with the system catalogs, and the answer is out of date the next time someone runs a GRANT. BareSQL Audit logs in, reads the catalogs inside a read-only transaction and writes the answer down: a report for people and a JSON file for the next audit to be compared with.&lt;/p&gt;</description>
    </item>
    <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>
