Skip to content

P
Postgres FD Implementation
Commit cfe71bd3 authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

Add URL for ISO date/time syntax: 

>
> 		  http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php
>
parent 28b0d6bf
Hide whitespace changes
Inline Side-by-side
Showing with 29 additions and 22 deletions
doc/TODO
View file @ cfe71bd3
...@@ -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 Jun 16 00:04:49 EDT 2006 Last updated: Fri Jun 16 12:59:22 EDT 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.
...@@ -255,6 +255,9 @@ Data Types ...@@ -255,6 +255,9 @@ Data Types
o Fix interval display to support values exceeding 2^31 hours o Fix interval display to support values exceeding 2^31 hours
o Add overflow checking to timestamp and interval arithmetic o Add overflow checking to timestamp and interval arithmetic
o Add ISO INTERVAL handling o Add ISO INTERVAL handling
http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php
o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO
SECOND SECOND
o Support ISO INTERVAL syntax if units cannot be determined from o Support ISO INTERVAL syntax if units cannot be determined from
......
doc/src/FAQ/TODO.html
View file @ cfe71bd3
...@@ -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 Jun 16 00:04:49 EDT 2006 Last updated: Fri Jun 16 12:59:22 EDT 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>.
...@@ -233,10 +233,14 @@ first. ...@@ -233,10 +233,14 @@ first.
</li><li>Fix interval display to support values exceeding 2^31 hours </li><li>Fix interval display to support values exceeding 2^31 hours
</li><li>Add overflow checking to timestamp and interval arithmetic </li><li>Add overflow checking to timestamp and interval arithmetic
</li><li>Add ISO INTERVAL handling </li><li>Add ISO INTERVAL handling
<ul> </li></ul>
<li>-<em>Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO </em> </li></ul>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php">http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php</a>
</p>
<ul>
<li>-<em>Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO </em>
SECOND SECOND
</li><li>Support ISO INTERVAL syntax if units cannot be determined from </li><li>Support ISO INTERVAL syntax if units cannot be determined from
the string, and are supplied after the string the string, and are supplied after the string
<p> The SQL standard states that the units 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 specify the units of the string, e.g. INTERVAL '2' MINUTE
...@@ -257,33 +261,33 @@ first. ...@@ -257,33 +261,33 @@ first.
range of units supported, e.g. PostgreSQL supports '1 year 1 range of units supported, e.g. PostgreSQL supports '1 year 1
hour', while the SQL standard does not. hour', while the SQL standard does not.
</p> </p>
</li><li>Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH </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 </li><li>Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS
INTERVAL MONTH), and this should return '12 months' INTERVAL MONTH), and this should return '12 months'
</li><li>Round or truncate values to the requested precision, e.g. </li><li>Round or truncate values to the requested precision, e.g.
INTERVAL '11 months' AS YEAR should return one or zero INTERVAL '11 months' AS YEAR should return one or zero
</li><li>Support precision, CREATE TABLE foo (a INTERVAL MONTH(3)) </li><li>Support precision, CREATE TABLE foo (a INTERVAL MONTH(3))
</li></ul>
</li></ul>
</li><li>Arrays
<ul> <ul>
<li>-<em>Allow NULLs in arrays</em> <li>Arrays
</li><li>Delay resolution of array expression's data type so assignment <ul>
<li>-<em>Allow NULLs in arrays</em>
</li><li>Delay resolution of array expression's data type so assignment
coercion can be performed on empty array expressions coercion can be performed on empty array expressions
</li></ul> </li></ul>
</li><li>Binary Data </li><li>Binary Data
<ul> <ul>
<li>Improve vacuum of large objects, like /contrib/vacuumlo? <li>Improve vacuum of large objects, like /contrib/vacuumlo?
</li><li>Add security checking for large objects </li><li>Add security checking for large objects
</li><li>Auto-delete large objects when referencing row is deleted </li><li>Auto-delete large objects when referencing row is deleted
<p> /contrib/lo offers this functionality. <p> /contrib/lo offers this functionality.
</p> </p>
</li><li>Allow read/write into TOAST values like large objects </li><li>Allow read/write into TOAST values like large objects
<p> This requires the TOAST column to be stored EXTERNAL. <p> This requires the TOAST column to be stored EXTERNAL.
</p> </p>
</li><li>Add API for 64-bit large object access </li><li>Add API for 64-bit large object access
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php">http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php</a> <p> <a href="http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php">http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php</a>
</p> </p>
</li></ul>
</li></ul> </li></ul>
</li></ul> </li></ul>
<h1><a name="section_5">Functions</a></h1> <h1><a name="section_5">Functions</a></h1>
......
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