From 7905a716955386411f176cc463e9bd2a82250e16 Mon Sep 17 00:00:00 2001
From: steve-chavez <stevechavezast@gmail.com>
Date: Mon, 18 Sep 2023 11:19:00 -0300
Subject: [PATCH] explanation: data independence

---
 docs/explanations/data_independence.rst | 10 ++++++++++
 1 file changed, 10 insertions(+)
 create mode 100644 docs/explanations/data_independence.rst

diff --git a/docs/explanations/data_independence.rst b/docs/explanations/data_independence.rst
new file mode 100644
index 000000000..283680dbf
--- /dev/null
+++ b/docs/explanations/data_independence.rst
@@ -0,0 +1,10 @@
+.. _data_independence:
+
+Data Independence
+#################
+
+  "Data independence means we have the freedom to change the physical database without changing the logical database and therefore all your investment in existing applications, existing retrieval requests, existing people, existing training, existing database designs; all of that is still good. Data independence translates into protecting the users investment."
+
+  -- C.J. Date
+
+Data Independence in PostgreSQL can be achieved by hiding tables from users and only exposing them views. PostgREST also proposes an additional way by using :ref:`domain_reps`.