MIME-Version: 1.0
References: 
 <CAPnyYmzMA4TU5i+3ZgTsbC7wfYy9wSMKz=+yjC9q9ZF47NBbnA@mail.gmail.com>
In-Reply-To: 
 <CAPnyYmzMA4TU5i+3ZgTsbC7wfYy9wSMKz=+yjC9q9ZF47NBbnA@mail.gmail.com>
From: Dave Page <dpage@pgadmin.org>
Date: Mon, 2 Jun 2025 15:45:51 +0100
Message-ID: 
 <CA+OCxowm--WdiC3k57i3SiyX0uMExayF6Fsdrq+HSQ-EcEvkxA@mail.gmail.com>
Subject: Re: BEGIN/END in SQL generated by pgAdmin ERD command
To: Marc Linster <marc@marclinster.com>
Cc: pgadmin-support <pgadmin-support@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000b6ee0b063697d296"
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2BOCxowm--WdiC3k57i3SiyX0uMExayF6Fsdrq%2BHSQ-EcEvkxA%40mail.gmail.com>
Precedence: bulk

--000000000000b6ee0b063697d296
Content-Type: text/plain; charset="UTF-8"

Hi

On Mon, 2 Jun 2025 at 15:30, Marc Linster <marc@marclinster.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

--000000000000b6ee0b063697d296
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi</div><br><div class=3D"gmail_quote gmail_quote_con=
tainer"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, 2 Jun 2025 at 15:30, =
Marc Linster &lt;<a href=3D"mailto:marc@marclinster.com">marc@marclinster.c=
om</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-le=
ft-color:rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>When I as=
k pgAdmin 9.4 to generate SQL from the ERD window, it wraps &#39;BEGIN;&#39=
; and &#39;END;&#39; around the set of statements, instead of &#39;BEGIN;/C=
OMMIT;&#39;.</div><div><br></div><div>This is for pgAdmin 9.4 on Sequoia 15=
.5</div><div><br></div><div>Am I missing something?</div></div></blockquote=
><div><br></div><div>END is the same as COMMIT, albeit PostgreSQL specific =
and not part of the SQL standard.</div><div><br></div><div><a href=3D"https=
://www.postgresql.org/docs/17/sql-end.html">https://www.postgresql.org/docs=
/17/sql-end.html</a></div><div><br></div><div>It would probably be nice to =
change it to COMMIT if someone felt inclined, but it&#39;s not a bug.=C2=A0=
</div></div><div><br></div><span class=3D"gmail_signature_prefix">-- </span=
><br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr">Dave Page<=
div>pgAdmin: <a href=3D"https://www.pgadmin.org" target=3D"_blank">https://=
www.pgadmin.org</a></div><div>PostgreSQL: <a href=3D"https://www.postgresql=
.org" target=3D"_blank">https://www.postgresql.org</a></div><div>pgEdge: <a=
 href=3D"https://www.pgedge.com" target=3D"_blank">https://www.pgedge.com</=
a><br><div></div><div><br></div></div></div></div></div>

--000000000000b6ee0b063697d296--