diff --git a/doc/TODO b/doc/TODO index 624719f07eaa282c1d2c4a12e6cb04dce8ef85b0..4a79986b64bb25ca89cf410b8beec04e17c8970a 100644 --- 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 diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 58e55c44c3ebaf18d1bb6aa8079399b16f656078..cc00512a4be8b04c68680b9434e5b1424307e319 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,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. @@ -225,24 +225,24 @@ first. SECOND

  • 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.

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