Word wrap entry

f04080d7 · Bruce Momjian · c880f9ae · f04080d7 · f04080d7
隐藏空白更改
内联并排

Showing with 32 addition and 32 deletion

doc/TODO doc/TODO +16 -16

doc/src/FAQ/TODO.html doc/src/FAQ/TODO.html +16 -16

未找到文件。
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:	Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated:		Mon Apr 24 20:00:38 EDT 2006
+Last updated:		Mon Apr 24 20:06:13 EDT 2006

 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -244,24 +244,24 @@ Data Types
 		o Support ISO INTERVAL syntax if units cannot be determined from
 		  the string, and are supplied after the string

-		  The SQL standard states that the units after the string specify
-		  the units of the string, e.g. INTERVAL '2' MINUTE should
-		  return '00:02:00'.  The current behavior has the units
-		  restrict the interval value to the specified unit or unit range,
-		  INTERVAL '70' SECOND returns '00:00:10'.
+		  The SQL standard states that the units after the string
+		  specify the units of the string, e.g. INTERVAL '2' MINUTE
+		  should return '00:02:00'. The current behavior has the units
+		  restrict the interval value to the specified unit or unit
+		  range, INTERVAL '70' SECOND returns '00:00:10'.

 		  For syntax that isn't uniquely ISO or PG syntax, like '1' or
 		  '1:30', treat as ISO if there is a range specification clause,
-	          and as PG if there no clause is present, e.g. interpret
-		  '1:30' MINUTE TO SECOND as '1 minute 30 seconds', and
-		  interpret '1:30' as '1 hour, 30 minutes'.
-
-		  This makes common cases like SELECT INTERVAL '1' MONTH 
-		  SQL-standard results.  The SQL standard supports a limited
-		  number of unit combinations and doesn't support unit names
-		  in the string.  The PostgreSQL syntax is more flexible in
-                  the range of units supported, e.g. PostgreSQL supports 
-		  '1 year 1 hour', while the SQL standard does not.
+		  and as PG if there no clause is present, e.g. interpret '1:30'
+		  MINUTE TO SECOND as '1 minute 30 seconds', and interpret
+		  '1:30' as '1 hour, 30 minutes'.
+
+		  This makes common cases like SELECT INTERVAL '1' MONTH
+		  SQL-standard results. The SQL standard supports a limited
+		  number of unit combinations and doesn't support unit names in
+		  the string. The PostgreSQL syntax is more flexible in the
+		  range of units supported, e.g. PostgreSQL supports '1 year 1
+		  hour', while the SQL standard does not.

 		o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH
 		o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS

--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
 <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
 <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/>
-Last updated:           Mon Apr 24 20:00:38 EDT 2006
+Last updated:           Mon Apr 24 20:06:13 EDT 2006
 </p>
 <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>.
@@ -225,24 +225,24 @@ first.
                  SECOND
      </li><li>Support ISO INTERVAL syntax if units cannot be determined from
                  the string, and are supplied after the string
-<p>                  The SQL standard states that the units after the string specify
-                  the units of the string, e.g. INTERVAL '2' MINUTE should
-                  return '00:02:00'.  The current behavior has the units
-                  restrict the interval value to the specified unit or unit range,
-                  INTERVAL '70' SECOND returns '00:00:10'.
+<p>                  The SQL standard states that the units after the string
+                  specify the units of the string, e.g. INTERVAL '2' MINUTE
+                  should return '00:02:00'. The current behavior has the units
+                  restrict the interval value to the specified unit or unit
+                  range, INTERVAL '70' SECOND returns '00:00:10'.
 </p>
 <p>                  For syntax that isn't uniquely ISO or PG syntax, like '1' or
                  '1:30', treat as ISO if there is a range specification clause,
-                  and as PG if there no clause is present, e.g. interpret
-                  '1:30' MINUTE TO SECOND as '1 minute 30 seconds', and
-                  interpret '1:30' as '1 hour, 30 minutes'.
-</p>
-<p>                  This makes common cases like SELECT INTERVAL '1' MONTH 
-                  SQL-standard results.  The SQL standard supports a limited
-                  number of unit combinations and doesn't support unit names
-                  in the string.  The PostgreSQL syntax is more flexible in
-                  the range of units supported, e.g. PostgreSQL supports 
-                  '1 year 1 hour', while the SQL standard does not.
+                  and as PG if there no clause is present, e.g. interpret '1:30'
+                  MINUTE TO SECOND as '1 minute 30 seconds', and interpret
+                  '1:30' as '1 hour, 30 minutes'.
+</p>
+<p>                  This makes common cases like SELECT INTERVAL '1' MONTH
+                  SQL-standard results. The SQL standard supports a limited
+                  number of unit combinations and doesn't support unit names in
+                  the string. The PostgreSQL syntax is more flexible in the
+                  range of units supported, e.g. PostgreSQL supports '1 year 1
+                  hour', while the SQL standard does not.
 </p>
      </li><li>Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH
      </li><li>Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS