Commit 97d37b7a authored by Bruce Momjian's avatar Bruce Momjian

Done:

< 	o Improve psql's handling of multi-line statements
> 	o -Improve psql's handling of multi-line statements
parent 4cb27fef
...@@ -2,7 +2,7 @@ ...@@ -2,7 +2,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Last updated: Fri Feb 10 22:33:33 EST 2006 Last updated: Sat Feb 11 16:55:42 EST 2006
The most recent version of this document can be viewed at The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. http://www.postgresql.org/docs/faqs.TODO.html.
...@@ -599,7 +599,7 @@ Clients ...@@ -599,7 +599,7 @@ Clients
o Allow psql \pset boolean variables to set to fixed values, rather o Allow psql \pset boolean variables to set to fixed values, rather
than toggle than toggle
o Consistently display privilege information for all objects in psql o Consistently display privilege information for all objects in psql
o Improve psql's handling of multi-line statements o -Improve psql's handling of multi-line statements
Currently, while \e saves a single statement as one entry, interactive Currently, while \e saves a single statement as one entry, interactive
statements are saved one line at a time. Ideally all statements statements are saved one line at a time. Ideally all statements
......
...@@ -8,7 +8,7 @@ ...@@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1> <h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/> <p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
Last updated: Fri Feb 10 22:33:33 EST 2006 Last updated: Sat Feb 11 16:55:42 EST 2006
</p> </p>
<p>The most recent version of this document can be viewed at<br/> <p>The most recent version of this document can be viewed at<br/>
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>. <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
...@@ -546,7 +546,7 @@ first. ...@@ -546,7 +546,7 @@ first.
</li><li>Allow psql \pset boolean variables to set to fixed values, rather </li><li>Allow psql \pset boolean variables to set to fixed values, rather
than toggle than toggle
</li><li>Consistently display privilege information for all objects in psql </li><li>Consistently display privilege information for all objects in psql
</li><li>Improve psql's handling of multi-line statements </li><li>-<em>Improve psql's handling of multi-line statements</em>
<p> Currently, while \e saves a single statement as one entry, interactive <p> Currently, while \e saves a single statement as one entry, interactive
statements are saved one line at a time. Ideally all statements statements are saved one line at a time. Ideally all statements
would be saved like \e does. would be saved like \e does.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment