# Proposal: Virtual Storage Columns (Seamless DB-to-Storage Mapping)

The Problem: Storage vs. Database Friction Currently, managing files in Supabase requires developers to bridge two distinct mental models: the Relational Database and Object Storage. This creates several DX hurdles: 1. Multi-step Workflows: Developers must upload a file, wait for a path/URL, and then perform a second update or insert to the database. 2. Syncing Permissions: Security logic often has to be duplicated—once for the Database RLS and once for the Storage Bucket RLS. 3. Binary Inefficiency: To avoid the complexity above, some developers store files as BYTEA (binary) directly in tables, which is inefficient and scales poorly. The Solution: Virtual Storage Columns I am proposing a Mapping Layer that allows developers to treat storage objects as first-class citizens within a PostgreSQL table. Under the hood, it uses existing Storage buckets, but the "mental model" is that of a simple table column. How it Works • The Column: We introduce a sp…