MIME-Version: 1.0
References: <CAJMpnG5FxZw7dJd+EUu19GoETShT_AUGqx1SG6hsyMoTOH61=w@mail.gmail.com>
In-Reply-To: <CAJMpnG5FxZw7dJd+EUu19GoETShT_AUGqx1SG6hsyMoTOH61=w@mail.gmail.com>
From: Lorusso Domenico <domenico.l76@gmail.com>
Date: Thu, 11 Sep 2025 17:09:31 +0200
Message-ID: <CAJMpnG5X60mDNN9Sbz8syznADHes2QqNmXvv1ZA4yzqYSeWJPw@mail.gmail.com>
Subject: =?UTF-8?Q?Re=3A_=5BAnnouncement=5D_=E2=80=8BA_Bitemporal_Solution_for_Post?=
	=?UTF-8?Q?greSQL_=28Beta=29?=
To: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000be2a0a063e87eef6"
Archived-At: <https://www.postgresql.org/message-id/CAJMpnG5X60mDNN9Sbz8syznADHes2QqNmXvv1ZA4yzqYSeWJPw%40mail.gmail.com>
Precedence: bulk

--000000000000be2a0a063e87eef6
Content-Type: text/plain; charset="UTF-8"

sorry here the link https://github.com/DomenicoL/table-versioning/


Il giorno gio 11 set 2025 alle ore 17:08 Lorusso Domenico <
domenico.l76@gmail.com> ha scritto:

> Dear all,
>
> I am gald to share an open-source project I've been developing in my free
> time. It's a bitemporal solution built entirely within PostgreSQL, and
> while it's still in its early beta stages, it has the ambition to provide a
> comprehensive framework for temporal data management. The project is
> inspired by the need for a simple, yet powerful way to handle historical
> records and query data as it existed at any point in time.
>
> This solution is designed to be highly configurable and uses views with INSTEAD
> OF triggers to seamlessly manage inserts, updates, and deletes across
> _current and _history tables. Key features include:
>
>    -
>
>    *Bitemporal Support*: Tracks both "valid time" (when a fact is true in
>    the real world) and "transaction time" (when the fact was recorded in the
>    database).
>    -
>
>    *Automatic Historicization*: The system automatically creates and
>    manages historical records, ensuring a complete, immutable audit trail.
>    -
>
>    *Trigger-based Logic*: The core logic is encapsulated in a
>    vrsn.trigger_handler() function, making it easy to apply to any table
>    via a view.
>    -
>
>    *Configurable Behavior*: A set of parameters and state variables (
>    vrsn.tar_state_variables) allows for fine-grained control over
>    versioning, conflict resolution, and other behaviors.
>    -
>
>    *Adherence to Bitemporal Theory*: The framework is designed to be
>    fully compliant with the bitemporal model proposed by Snodgrass.
>    -
>
>    *Pure SQL & Transparency*: The solution is built using pure PostgreSQL
>    functions and types, requiring *no external extensions*, and it
>    maintains a *transparent data structure* that does not mask the
>    underlying tables.
>
> This project is a work in progress, and I would love to get your feedback
> and collaboration to improve it. If the concept interests you and you'd
> like to dive into the code or offer some guidance, your expertise would be
> highly valued.
>
> Thank you for your time and consideration.
>
> Bye
>
>
> --
> Domenico L.
>
>

-- 
Domenico L.

per stupire mezz'ora basta un libro di storia,
io cercai di imparare la Treccani a memoria... [F.d.A.]

--000000000000be2a0a063e87eef6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:garamond=
,serif;font-size:large">sorry here the link=C2=A0<a href=3D"https://github.=
com/DomenicoL/table-versioning/">https://github.com/DomenicoL/table-version=
ing/</a></div><div class=3D"gmail_default" style=3D"font-family:garamond,se=
rif;font-size:large"><br></div></div><br><div class=3D"gmail_quote gmail_qu=
ote_container"><div dir=3D"ltr" class=3D"gmail_attr">Il giorno gio 11 set 2=
025 alle ore 17:08 Lorusso Domenico &lt;<a href=3D"mailto:domenico.l76@gmai=
l.com">domenico.l76@gmail.com</a>&gt; ha scritto:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div><div class=3D"gmail=
_default" style=3D"font-family:garamond,serif;font-size:large"><span style=
=3D"font-family:Arial,Helvetica,sans-serif;font-size:small">Dear all,</span=
></div><p><span>I am gald to share an open-source project I&#39;ve been dev=
eloping in my free time. It&#39;s a bitemporal solution built entirely with=
in PostgreSQL, and while it&#39;s still in its early beta stages, it has th=
e ambition to provide a comprehensive framework for temporal data managemen=
t. The project is inspired by the need for a simple, yet powerful way to ha=
ndle historical records and query data as it existed at any point in time.<=
/span></p><p><span>This solution is designed to be highly configurable and =
uses views with </span><code><span>INSTEAD OF</span></code><span> triggers =
to seamlessly manage inserts, updates, and deletes across </span><code><spa=
n>_current</span></code><span> and </span><code><span>_history</span></code=
><span> tables. Key features include:</span></p><ul><li><p><strong><span>Bi=
temporal Support</span></strong><span>: Tracks both &quot;valid time&quot; =
(when a fact is true in the real world) and &quot;transaction time&quot; (w=
hen the fact was recorded in the database).</span></p></li><li><p><strong><=
span>Automatic Historicization</span></strong><span>: The system automatica=
lly creates and manages historical records, ensuring a complete, immutable =
audit trail.</span></p></li><li><p><strong><span>Trigger-based Logic</span>=
</strong><span>: The core logic is encapsulated in a </span><code><span>vrs=
n.trigger_handler()</span></code><span> function, making it easy to apply t=
o any table via a view.</span></p></li><li><p><strong><span>Configurable Be=
havior</span></strong><span>: A set of parameters and state variables (</sp=
an><code><span>vrsn.tar_state_variables</span></code><span>) allows for fin=
e-grained control over versioning, conflict resolution, and other behaviors=
.</span></p></li><li><p><strong><span>Adherence to Bitemporal Theory</span>=
</strong><span>: The framework is designed to be fully compliant with the b=
itemporal model proposed by Snodgrass.</span></p></li><li><p><strong><span>=
Pure SQL &amp; Transparency</span></strong><span>: The solution is built us=
ing pure PostgreSQL functions and types, requiring </span><strong><span>no =
external extensions</span></strong><span>, and it maintains a </span><stron=
g><span>transparent data structure</span></strong><span> that does not mask=
 the underlying tables.</span></p></li></ul><p><span>This project is a work=
 in progress, and I would love to get your feedback and collaboration to im=
prove it. If the concept interests you and you&#39;d like to dive into the =
code or offer some guidance, your expertise would be highly valued.</span><=
/p><p><span>Thank you for your time and consideration.</span></p><p><span><=
span class=3D"gmail_default" style=3D"font-family:garamond,serif;font-size:=
large">B</span><span class=3D"gmail_default" style=3D"font-family:garamond,=
serif;font-size:large">ye</span></span></p><br clear=3D"all"></div><div><br=
></div><span class=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr=
" class=3D"gmail_signature">Domenico L.<br><br></div></div>
</blockquote></div><div><br clear=3D"all"></div><div><br></div><span class=
=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_s=
ignature">Domenico L.<br><br>per stupire mezz&#39;ora basta un libro di sto=
ria,<br>io cercai di imparare la Treccani a memoria... [F.d.A.]</div>

--000000000000be2a0a063e87eef6--