MIME-Version: 1.0
References: <84A5765B-1D3C-485B-B852-99D63D53963E@meddatainc.com>
 <4835994a-aecf-4fef-bb75-9a4c5f6e0ffd@aklaver.com> <EEE7D9EB-CDFE-420F-9A84-A51E80EC644B@meddatainc.com>
In-Reply-To: <EEE7D9EB-CDFE-420F-9A84-A51E80EC644B@meddatainc.com>
From: Francisco Olarte <folarte@peoplecall.com>
Date: Mon, 10 Mar 2025 20:27:02 +0100
Message-ID: <CA+bJJbzgiri9pU2=dzB-Ru24bYHA=xBn-TPr1sjg=sDqtixYYQ@mail.gmail.com>
Subject: Re: Creating files with testdata
To: H <agents@meddatainc.com>
Cc: pgsql-general@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://www.postgresql.org/message-id/CA%2BbJJbzgiri9pU2%3DdzB-Ru24bYHA%3DxBn-TPr1sjg%3DsDqtixYYQ%40mail.gmail.com>
Precedence: bulk

On Mon, 10 Mar 2025 at 20:18, H <agents@meddatainc.com> wrote:
> There are tables referencing each other using randomly generated IDs, ie. those IDs are not known until after the parent table row is inserted.

Random? Then they CAN collide. ;->

Do the IDs need to be random or are they just the default value?

I've encountered a similar problem with sequences and have bypassed it
by using explicit values into the test data, i.e.m, inserting an
invoice with id 1000 followed by its lines with IDs 100010, 100011,
.... and then setting start_values for the sequences at 99999999. This
helped me a lot in a debugging. You could do the same depending on
what domain your random ids are on.

Francisco Olarte.