Re: sql developer vs sqlplus sql and plsql syntax

From: William Robertson <>
Date: Sun, 13 Dec 2020 23:24:42 +0000
Message-Id: <>

Because it's valid syntax in those languages. Requiring everyone to include the same terminating symbols as the SQL*Plus default settings might be convenient for your forgetful developers at deployment time, but it would be a redundant annoyance for everyone else.

Oracle SQL has no semicolon character. Even SQL*Plus doesn't require it, it's just the default. PL/SQL doesn't have a block terminator character.

Desktop tools can optionally add slash characters in their Save As features. I don't know about SQL Developer but PL/SQL has this as a preference setting for Program Windows.

On 13 Dec 2020, at 18:19, Ls Cheng <> wrote:


This is for Jeff Smith! :-)

I would like to know why SQL Developer allow people to execute SQL code without semicolon and PLSQL code with backslash? (OK TOAD does the same thing but it is not made by Oracle)

For example code such as this works in SQL developer

  • semicolon missing select * from dba_users
  • backslash missing declare l_a number; begin select 1 into l_a from dual; end;
  • backslash missing create or replace procedure p_test is l_a number; begin select 1 into l_a from dual; end;

This is causing some serious conflicts between DBA team and the developers because the developers write codes in SQL developer then they upload them as script for the DBA to run in the test/prod environment which all fails (and plsql objects not created) obecause DBA's uses SQLPLUS and because most SQL execution request are batched with SQLPLUS.

The developers claim if the code runs in SQL developer it must run in SQLPLUS because it is a tool from Oracle. Is there a way to configure SQL Developer so it can have the same behaviour as SQLPLUS?


Received on Mon Dec 14 2020 - 00:24:42 CET

Original text of this message