From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Multiple tables row insertions from single psql input file |
Date: | 2024-06-10 20:25:54 |
Message-ID: | CANzqJaBiwqb_9c-+Ot1YL3UtQsrDb9K7RO0unD2r3jFH7uxNSA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jun 10, 2024 at 4:06 PM Rich Shepard <rshepard(at)appl-ecosys(dot)com>
wrote:
> On Mon, 10 Jun 2024, Ron Johnson wrote:
>
> > With enough clever scripting you can create a .sql file that does almost
> > anything.
>
> Ron,
>
> My projects don't all use SQL so I'm far from a clever scripter. :-)
>
No one is born a scripter, much less a clever scripter.
> > Most useful to you will be some number of "ALTER TABLE <foo> DISABLE
> > TRIGGER ALL;" statements near the beginning of the file, and their "ALTER
> > TABLE ... ENABLE TRIGGER ALL;" counterparts near the end of the file.
>
> Doesn't alter table primarily apply to existing row values for specific
> columns rather than inserting new rows and their column values?
>
I don't think so. For example, pg_dump has an option to add those
DISABLE/ENABLE TRIGGER statements. It makes bulk loading of records much
simpler.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2024-06-10 20:52:53 | Re: Escaping single quotes with backslash seems not to work |
Previous Message | Adrian Klaver | 2024-06-10 20:20:45 | Re: Does trigger only accept functions? |