database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-27 22:56:53 +03:00
Code

Add URL for ISO date/time syntax:

Browse Source 
>
> 		  http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php
>
This commit is contained in:
Bruce Momjian 2006-06-16 16:59:30 +00:00
parent 28b0d6bf62
commit cfe71bd35d
2 changed files with 29 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/TODO
View File

@ -2,7 +2,7 @@
PostgreSQL TODO List
====================
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
http://www.postgresql.org/docs/faqs.TODO.html.
@ -255,6 +255,9 @@ Data Types
o Fix interval display to support values exceeding 2^31 hours
o Add overflow checking to timestamp and interval arithmetic
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
SECOND
o Support ISO INTERVAL syntax if units cannot be determined from

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

@ -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: Fri Jun 16 00:04:49 EDT 2006
Last updated: Fri Jun 16 12:59:22 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>.
@ -233,10 +233,14 @@ first.
</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 ISO INTERVAL handling
<ul>
<li>-<em>Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO </em>
</li></ul>
</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
</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
<p> The SQL standard states that the units after the string
specify the units of the string, e.g. INTERVAL '2' MINUTE
@ -257,33 +261,33 @@ first.
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
</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
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
</li><li>Support precision, CREATE TABLE foo (a INTERVAL MONTH(3))
</li></ul>
</li></ul>
</li><li>Arrays
</li><li>Support precision, CREATE TABLE foo (a INTERVAL MONTH(3))
<ul>
<li>-<em>Allow NULLs in arrays</em>
</li><li>Delay resolution of array expression's data type so assignment
<li>Arrays
<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
</li></ul>
</li><li>Binary Data
<ul>
<li>Improve vacuum of large objects, like /contrib/vacuumlo?
</li><li>Add security checking for large objects
</li><li>Auto-delete large objects when referencing row is deleted
</li></ul>
</li><li>Binary Data
<ul>
<li>Improve vacuum of large objects, like /contrib/vacuumlo?
</li><li>Add security checking for large objects
</li><li>Auto-delete large objects when referencing row is deleted
<p> /contrib/lo offers this functionality.
</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>
</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>
</li></ul>
</li></ul>
</li></ul>
<h1><a name="section_5">Functions</a></h1>