Re: Best way to store Master-Detail Data

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Alvin Díaz <alvin(dot)rd(at)live(dot)com>
Cc: "pgsql-sql(at)postgresql(dot)org" <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Best way to store Master-Detail Data
Date: 2017-04-13 04:15:29
Message-ID: CAKFQuwY0JktnMUiNziPhCcX9xt1kz1e4x1YpDFck2iH-LdyqHg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Wednesday, April 12, 2017, Alvin Díaz <alvin(dot)rd(at)live(dot)com> wrote:

> the same function to make sure that both
> header and detail
> are committed or not.
>

You don't need functions to establish transactions. That is why the
commands BEGIN and COMMIT exist.

David J.

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Andreas Kretschmer 2017-04-13 10:54:53 Re: Best way to store Master-Detail Data
Previous Message Alvin Díaz 2017-04-13 03:51:36 Best way to store Master-Detail Data