pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jonathan Zacharuk <jonathan.zacharuk@ascentech.ca>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: RE: Error when using unquoted identifier that contains the word end in a begin atomic block
Date: Thu, 24 Aug 2023 20:23:00 +0000
Message-ID: <YT2PR01MB431868625CDBA6086F22A0359C1DA@YT2PR01MB4318.CANPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <3972353.1692907946@sss.pgh.pa.us>
References: <YT2PR01MB4318B3BD0B4D84546C3EAC169C1DA@YT2PR01MB4318.CANPRD01.PROD.OUTLOOK.COM>
	<3972353.1692907946@sss.pgh.pa.us>

Thanks Tom. I should have noticed that the command I was running was not completely getting sent to the server. This does indeed look like a Navicat issue. I have confirmed with psql that this works fine and will ensure to do so in the future!

-----Original Message-----
From: Tom Lane <tgl@sss.pgh.pa.us> 
Sent: Thursday, August 24, 2023 1:12 PM
To: Jonathan Zacharuk <jonathan.zacharuk@ascentech.ca>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Error when using unquoted identifier that contains the word end in a begin atomic block

Jonathan Zacharuk <jonathan.zacharuk@ascentech.ca> writes:
> It seems to me that within a BEGIN ATOMIC block the use of the word "end" within an unquoted identifier is causing an error.

I think your problem is somewhere on the client side.

> -- This function is successfully created (note the quoted "effective_end_date").
> CREATE OR REPLACE FUNCTION test_function_success() RETURNS TIMESTAMP 
> LANGUAGE SQL BEGIN ATOMIC
>   SELECT DISTINCT "effective_end_date"
>                 FROM test_view;
> END

For me, this works (in psql) with or without the double quotes:

regression=# CREATE OR REPLACE FUNCTION test_function_success() RETURNS TIMESTAMP LANGUAGE SQL BEGIN ATOMIC
  SELECT DISTINCT "effective_end_date"
                FROM test_view;
END;
CREATE FUNCTION
regression=# CREATE OR REPLACE FUNCTION test_function_success() RETURNS TIMESTAMP LANGUAGE SQL BEGIN ATOMIC
  SELECT DISTINCT effective_end_date
                FROM test_view;
END;
CREATE FUNCTION

> -- This function fails to be created. I would expect this to work.
> CREATE OR REPLACE FUNCTION test_function_fail() RETURNS TIMESTAMP 
> LANGUAGE SQL BEGIN ATOMIC
>   SELECT DISTINCT effective_end_date
>                 FROM test_view
> ERROR:  syntax error at end of input
> LINE 6:  FROM test_view
>                        ^

I can't help noticing that the trailing END is missing from what you show here, and it seems pretty clear that the syntax error is about that, not about the effective_end_date identifier.  So the real question is why the CREATE FUNCTION command is getting sent to the server before it's complete.  If this isn't flat-out pilot error, then I guess whatever client you are using (apparently not psql) is getting confused about which occurrence of "end" terminates the command.  You should take this up with the authors of said client software.

			regards, tom lane





view thread (3+ messages)

Message-ID: <YT2PR01MB431868625CDBA6086F22A0359C1DA@YT2PR01MB4318.CANPRD01.PROD.OUTLOOK.COM>
Permalink:  ../YT2PR01MB431868625CDBA6086F22A0359C1DA@YT2PR01MB4318.CANPRD01.PROD.OUTLOOK.COM/
Also on:    postgresql.org/message-id/YT2PR01MB431868625CDBA6086F22A0359C1DA@YT2PR01MB4318.CANPRD01.PROD.OUTLOOK.COM

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: jonathan.zacharuk@ascentech.ca, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
  Subject: RE: Error when using unquoted identifier that contains the word end in a begin atomic block
  In-Reply-To: <YT2PR01MB431868625CDBA6086F22A0359C1DA@YT2PR01MB4318.CANPRD01.PROD.OUTLOOK.COM>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox