Commit 5c9a46f6 authored by Bruce Momjian's avatar Bruce Momjian

Add:

* %Make row-wise comparisons work per SQL spec

  Right now, '(a, b) < (1, 2)' is processed as 'a < 1 and b < 2', but
  the SQL standard requires it to be processed as a column-by-column
  comparison, so the proper comparison is '(a < 1) OR (a = 1 AND b < 2)'.
parent 97e1535f
...@@ -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: Thu Dec 22 18:05:31 EST 2005 Last updated: Mon Dec 26 00:14:46 EST 2005
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.
...@@ -391,6 +391,11 @@ SQL Commands ...@@ -391,6 +391,11 @@ SQL Commands
* %Add COMMENT ON for all cluster global objects (roles, databases * %Add COMMENT ON for all cluster global objects (roles, databases
and tablespaces) and tablespaces)
* %Make row-wise comparisons work per SQL spec * %Make row-wise comparisons work per SQL spec
Right now, '(a, b) < (1, 2)' is processed as 'a < 1 and b < 2', but
the SQL standard requires it to be processed as a column-by-column
comparison, so the proper comparison is '(a < 1) OR (a = 1 AND b < 2)'.
* Add RESET CONNECTION command to reset all session state * Add RESET CONNECTION command to reset all session state
This would include resetting of all variables (RESET ALL), dropping of This would include resetting of all variables (RESET ALL), dropping of
......
...@@ -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: Thu Dec 22 18:05:31 EST 2005 Last updated: Mon Dec 26 00:14:46 EST 2005
</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>.
...@@ -359,6 +359,10 @@ first. ...@@ -359,6 +359,10 @@ first.
</li><li>%Add COMMENT ON for all cluster global objects (roles, databases </li><li>%Add COMMENT ON for all cluster global objects (roles, databases
and tablespaces) and tablespaces)
</li><li>%Make row-wise comparisons work per SQL spec </li><li>%Make row-wise comparisons work per SQL spec
<p> Right now, '(a, b) &lt; (1, 2)' is processed as 'a &lt; 1 and b &lt; 2', but
the SQL standard requires it to be processed as a column-by-column
comparison, so the proper comparison is '(a &lt; 1) OR (a = 1 AND b &lt; 2)'.
</p>
</li><li>Add RESET CONNECTION command to reset all session state </li><li>Add RESET CONNECTION command to reset all session state
<p> This would include resetting of all variables (RESET ALL), dropping of <p> This would include resetting of all variables (RESET ALL), dropping of
temporary tables, removing any NOTIFYs, cursors, open transactions, temporary tables, removing any NOTIFYs, cursors, open transactions,
......
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