Re: [HACKERS] psql and comments - Mailing list pgsql-hackers

From Thomas Lockhart
Subject Re: [HACKERS] psql and comments
Date
Msg-id 37FCA084.ADB71A9B@alumni.caltech.edu
Whole thread Raw
In response to Re: [HACKERS] psql and comments  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: [HACKERS] psql and comments  (Bruce Momjian <maillist@candle.pha.pa.us>)
Re: [HACKERS] psql and comments  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
> > The following example shows psql correctly clearing its input buffer
> > when a line containing *only* a comment is seen, but not completely
> > clearing the buffer (or not realizing that it is cleared; note the
> > changed prompt) if the comment is at the end of a valid query.
> >
> > postgres=> -- comment
> > postgres=> select 'hi'; -- comment
> > ?column?
> > --------
> > hi
> > (1 row)
> >
> > postgres->
> But aren't they _in_ a new statement, that begins with '--'?

?? Sure, that's what psql thinks. But the first case shown above
should also begin a new statement, changing the prompt (it doesn't,
because after stripping the comment there are zero blanks in the
line). I don't think that is the right behavior though.

Things aren't a big problem the way they stand, but istm that a
completely blank line (after stripping single-line comments) may as
well be the same as an empty line,and that psql could figure that out.
                   - Thomas

-- 
Thomas Lockhart                lockhart@alumni.caltech.edu
South Pasadena, California


pgsql-hackers by date:

Previous
From: Thomas Lockhart
Date:
Subject: Re: [HACKERS] Re: [GENERAL] Re: [PHP3] Re: PostgreSQL vs Mysql comparison
Next
From: wieck@debis.com (Jan Wieck)
Date:
Subject: Re: PostgreSQL Help