From: | Marc Linster <marc(at)marclinster(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | pgadmin-support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: BEGIN/END in SQL generated by pgAdmin ERD command |
Date: | 2025-06-03 09:18:04 |
Message-ID: | CAPnyYmxS8rd-XRjhZdr4_YRndrBysY4-G9WXLHERe82nvYVjyA@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Thanks Dave - I had an error message, but it turned out that was related to
my code.
M.
---------------------------------------
Marc Linster; Marc(at)MarcLinster(dot)com;
https://www.linkedin.com/in/marclinster;
https://marclinster.medium.com
+352 621 430 156
On Mon, Jun 2, 2025 at 4:46 PM Dave Page <dpage(at)pgadmin(dot)org> wrote:
> Hi
>
> On Mon, 2 Jun 2025 at 15:30, Marc Linster <marc(at)marclinster(dot)com> wrote:
>
>> When I ask pgAdmin 9.4 to generate SQL from the ERD window, it wraps
>> 'BEGIN;' and 'END;' around the set of statements, instead of
>> 'BEGIN;/COMMIT;'.
>>
>> This is for pgAdmin 9.4 on Sequoia 15.5
>>
>> Am I missing something?
>>
>
> END is the same as COMMIT, albeit PostgreSQL specific and not part of the
> SQL standard.
>
> https://www.postgresql.org/docs/17/sql-end.html
>
> It would probably be nice to change it to COMMIT if someone felt inclined,
> but it's not a bug.
>
> --
> Dave Page
> pgAdmin: https://www.pgadmin.org
> PostgreSQL: https://www.postgresql.org
> pgEdge: https://www.pgedge.com
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | B A | 2025-06-09 02:15:52 | Unable to access local server |
Previous Message | Murali Raghu (CTR) | 2025-06-02 20:57:55 | cannot locate my pgadmin 4 folder on windows 10 |