Re: Creating files with testdata
Francisco Olarte <folarte@peoplecall.com>
From: Francisco Olarte <folarte@peoplecall.com>
To: H <agents@meddatainc.com>
Cc: PostgreSQL Users Mailing List <pgsql-general@lists.postgresql.org>
Date: 2025-03-10T19:22:41Z
Lists: pgsql-general
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 scenario, 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.