database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-11-03 09:13:20 +03:00
Code Activity

Done:

Browse Source 
< * %Make row-wise comparisons work per SQL spec
> * -Make row-wise comparisons work per SQL spec
This commit is contained in:
Bruce Momjian
2005-12-28 02:12:25 +00:00
parent 6e07709760
commit 1b184c990f
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/TODO
View File

@@ -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: Mon Dec 26 00:14:46 EST 2005 Last updated: Tue Dec 27 21:12:26 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.
@@ -390,7 +390,7 @@ SQL Commands
creation creation
* %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 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 the SQL standard requires it to be processed as a column-by-column

4
doc/src/FAQ/TODO.html
View File

@@ -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: Mon Dec 26 00:14:46 EST 2005 Last updated: Tue Dec 27 21:12:26 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>.
@@ -358,7 +358,7 @@ first.
creation creation
</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>-<em>Make row-wise comparisons work per SQL spec</em>
<p> Right now, '(a, b) &lt; (1, 2)' is processed as 'a &lt; 1 and b &lt; 2', but <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 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)'. comparison, so the proper comparison is '(a &lt; 1) OR (a = 1 AND b &lt; 2)'.