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
On March 10, 2025 5:09:46 PM GMT-04:00, H wrote:
>On March 10, 2025 3:22:41 PM GMT-04:00, Francisco Olarte
> wrote:
>>On Mon, 10 Mar 2025 at 19:17, H 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 cr
On March 10, 2025 2:26:48 PM GMT-04:00, Adrian Klaver
wrote:
>
>
>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 te
On March 11, 2025 2:59:35 AM EDT, Thiemo Kellner
wrote:
>DbVisualizer
>https://www.dbvis.com/docs/ug/exporting-a-grid/?_gl=1*1aoko6w*_up*MQ..*_ga*MTA0NjM4MTcxNi4xNzQxNjc2MDc0*_ga_9P463C7BC6*MTc0MTY3NjA3My4xLjEuMTc0MTY3NjEyNC4wLjAuODQ3OTY1NDMx*_ga_PTZV59MQGC*MTc0MTY3NjA3My4xLjEuMTc0MTY3NjEyNC4wLjA
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 prede
On Mon, 10 Mar 2025 at 19:17, H 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 relatio
On Mon, Mar 10, 2025 at 12:17 PM H 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.
>
I just reserve half of the number space of bigint, the negatives, for test
data and assign known IDs as
On Mon, 10 Mar 2025 at 20:18, H 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 en
DbVisualizer
https://www.dbvis.com/docs/ug/exporting-a-grid/?_gl=1*1aoko6w*_up*MQ..*_ga*MTA0NjM4MTcxNi4xNzQxNjc2MDc0*_ga_9P463C7BC6*MTc0MTY3NjA3My4xLjEuMTc0MTY3NjEyNC4wLjAuODQ3OTY1NDMx*_ga_PTZV59MQGC*MTc0MTY3NjA3My4xLjEuMTc0MTY3NjEyNC4wLjAuMA..#generating-test-data
Or
DBeaver https://dbeaver.com
On March 10, 2025 3:15:10 PM EDT, H wrote:
>On March 10, 2025 2:26:48 PM GMT-04:00, Adrian Klaver
> wrote:
>>
>>
>>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 i
On March 10, 2025 3:27:02 PM GMT-04:00, Francisco Olarte
wrote:
>On Mon, 10 Mar 2025 at 20:18, H 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
On March 10, 2025 3:21:57 PM GMT-04:00, "David G. Johnston"
wrote:
>On Mon, Mar 10, 2025 at 12:17 PM H 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.
>>
>
>I just reserve half of the
On March 10, 2025 3:22:41 PM GMT-04:00, Francisco Olarte
wrote:
>On Mon, 10 Mar 2025 at 19:17, H 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.
13 matches
Mail list logo
