Some semicolon oddities
From: Stefan Ram <ram_at_zedat.fu-berlin.de>
Date: 25 Sep 2015 20:05:31 GMT
Message-ID: <semicolon-20150925205956_at_ram.dialup.fu-berlin.de>
When one enters »USE« into the client, no semicolon is needed:
Date: 25 Sep 2015 20:05:31 GMT
Message-ID: <semicolon-20150925205956_at_ram.dialup.fu-berlin.de>
When one enters »USE« into the client, no semicolon is needed:
USE S
. But when the USE is preceded by other commands on the same
line, it /does/ need a semicolon:
DROP SCHEMA D; CREATE SCHEMA D; USE D;
. I did not read this in the manual (is it in the manual at all?),
but observed it from the behavior of the client.
Now, one might say, »Ok, then I will /always/ add a semicolon, since I do not want to learn detailed rules about when it is needed.«, but sometimes a semicolon is not allowed as in
SOURCE C:\example.txt
, where a final semicolon would be treated as part of the
filepath IIRC.So, when entering client commands, sometimes we must add a semicolon, sometimes we may not, and sometimes both choices are possible. Received on Fri Sep 25 2015 - 22:05:31 CEST