From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | H <agents(at)meddatainc(dot)com>, PostgreSQL Users Mailing List <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Creating files with testdata |
Date: | 2025-03-10 18:26:48 |
Message-ID: | 4835994a-aecf-4fef-bb75-9a4c5f6e0ffd@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 3/10/25 11:09 AM, H wrote:
> I am developing a complex multi-tenant application in postgresql 16 in Linux. During the development I would like to be able to enter test data into various related tables at any given time for testing purposes.
>
> While this can certainly be accomplished by predefined CTE INSERT statements in an SQL file, I would prefer something more flexible. I am thinking of using a markdown file as a source for these CTE INSERT statements. Specifically, having a certain structure in the markdown file where a given markdown heading level, bullet level etc. would correspond to specific tables and columns.
Why CTE INSERTs?
>
> 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.
>
> Thanks.
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | H | 2025-03-10 19:15:10 | Re: Creating files with testdata |
Previous Message | H | 2025-03-10 18:09:15 | Creating files with testdata |