MIME-Version: 1.0
References: <84A5765B-1D3C-485B-B852-99D63D53963E@meddatainc.com>
In-Reply-To: <84A5765B-1D3C-485B-B852-99D63D53963E@meddatainc.com>
From: Francisco Olarte <folarte@peoplecall.com>
Date: Mon, 10 Mar 2025 20:22:41 +0100
Message-ID: <CA+bJJbyfE3NgyxBDb+Fp8ReZYQOZdit8jZF64PnE7ZVzzi=u0A@mail.gmail.com>
Subject: Re: Creating files with testdata
To: H <agents@meddatainc.com>
Cc: PostgreSQL Users Mailing List <pgsql-general@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CA%2BbJJbyfE3NgyxBDb%2BFp8ReZYQOZdit8jZF64PnE7ZVzzi%3Du0A%40mail.gmail.com>
Precedence: bulk

On Mon, 10 Mar 2025 at 19:17, H <agents@meddatainc.com> wrote:
...
> After entering my test data into the markdown file for the given test sce=
nario, I would then run an awk script or similar to create a SQL file with =
the various CTE INSERT statements. Howevever, it gets complex since I need =
to handle 1:N relationships between tables in the markdown file...
> I hope the above outline is understandable and am interested in comments =
and thoughts on my above approach.

I do not think MD would be a good source format. Being a developer I
would recommend taking your favorite scripting language ( perl /
python / lua / js , whatever ), build a big object ( which can be
easily helped by some mini-functions to build a little DSL ) and then
spit sql from it ( for developemewnt it is normally better then using
whatever db connection your language has, as it leaves an
understandable sql script ).

I have done this with perl for some projects, built a driver which
defined several helper functions, then dofile("xx.dat") which returned
a big hash and then a series of loops on the result to write the SQL
in whatever order was neccessary.

Francisco Olarte.