We are discussing the 'mysql' client which is often used to write
scripts that run under the
UNIX shell.
...
If you write a script that has two semi-colons in a row, the second one
is ignored and no error message is given.
Err, not true (in amysql script anyway)
I think you are trying
Pete French wrote:
We are discussing the 'mysql' client which is often used to write
scripts that run under the
UNIX shell.
...
If you write a script that has two semi-colons in a row, the second one
is ignored and no error message is given.
Err, not true (in amysql script anyway)
Hi,
I thought that I would report a very minor bug that I have just found in the mysql
command.
(Ver 11.13 Distrib 3.23.36)
If I do something like:
select * from foo where bar=123;;
I get the result of the select followed by:
ERROR:
No query specified
This is because I
[snip]
If I do something like:
select * from foo where bar=123;;
I get the result of the select followed by:
ERROR:
No query specified
This is because I have ';;' at the end of the line and it is complaining
about the empty command.
OK, I should not have typed it, but I
On Tue, Jul 23, 2002 at 07:38:42AM -0500, Jay Blanchard wrote:
[snip]
If I do something like:
select * from foo where bar=123;;
I get the result of the select followed by:
ERROR:
No query specified
This is because I have ';;' at the end of the line and it is complaining
Why do think this should not be an error?
If you were writing a script, would you not want to know you had made
the error?
Just how many , or how severe should errors be before you are notified?
Alain Williams wrote:
Hi,
I thought that I would report a very minor bug that I have just found
From: Gerald Clark [EMAIL PROTECTED]
Why do think this should not be an error?
If you were writing a script, would you not want to know you had made
the error?
Just how many , or how severe should errors be before you are notified?
The ability to run more than one query on one line is a
On Tue, Jul 23, 2002 at 11:59:43AM -0400, denonymous wrote:
From: Gerald Clark [EMAIL PROTECTED]
Why do think this should not be an error?
If you were writing a script, would you not want to know you had made
the error?
Just how many , or how severe should errors be before you are
[snip]
I quite agree that to have more than one command on a line is a nice thing.
What I am saying is that barfing on an empty command is not the right thing
to do.
I remember, many years ago, I wrote some coding standards where I said:
Every program/function should do nothing
Hi.
On Tue 2002-07-23 at 17:09:05 +0100, [EMAIL PROTECTED] wrote:
On Tue, Jul 23, 2002 at 11:59:43AM -0400, denonymous wrote:
[...]
The ability to run more than one query on one line is a feature, not a bug.
An empty semicolon is a badly-formed query. It's perfectly logical for the
Alain Williams wrote:
On Tue, Jul 23, 2002 at 11:59:43AM -0400, denonymous wrote:
From: Gerald Clark [EMAIL PROTECTED]
Why do think this should not be an error?
If you were writing a script, would you not want to know you had made
the error?
Just how many , or how severe should errors be
://www.calevans.com
*
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Benjamin
Pflugmann
Sent: Tuesday, July 23, 2002 2:06 PM
To: Alain Williams
Cc: denonymous; Gerald Clark; [EMAIL PROTECTED]
Subject: Re: Very minor buglet
IMO, it's the right thing. An empty command
12 matches
Mail list logo
