8
8
< body bgcolor ="#FFFFFF " text ="#000000 " link ="#FF0000 " vlink ="#A00000 " alink ="#0000FF ">
9
9
< h1 > < a name ="section_1 "> PostgreSQL TODO List</ a > </ h1 >
10
10
< p > Current maintainer: Bruce Momjian (< a href ="mailto:pgman@candle.pha.pa.us "> pgman@candle.pha.pa.us</ a > )< br />
11
- Last updated: Fri Jun 16 00:04:49 EDT 2006
11
+ Last updated: Fri Jun 16 12:59:22 EDT 2006
12
12
</ p >
13
13
< p > The most recent version of this document can be viewed at< br />
14
14
< a href ="http://www.postgresql.org/docs/faqs.TODO.html "> http://www.postgresql.org/docs/faqs.TODO.html</ a > .
@@ -233,10 +233,14 @@ <h1><a name="section_4">Data Types</a></h1>
233
233
</ li > < li > Fix interval display to support values exceeding 2^31 hours
234
234
</ li > < li > Add overflow checking to timestamp and interval arithmetic
235
235
</ li > < li > Add ISO INTERVAL handling
236
- < ul >
237
- < li > -< em > Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO </ em >
236
+ </ li > </ ul >
237
+ </ li > </ ul >
238
+ < p > < a href ="http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php "> http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php</ a >
239
+ </ p >
240
+ < ul >
241
+ < li > -< em > Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO </ em >
238
242
SECOND
239
- </ li > < li > Support ISO INTERVAL syntax if units cannot be determined from
243
+ </ li > < li > Support ISO INTERVAL syntax if units cannot be determined from
240
244
the string, and are supplied after the string
241
245
< p > The SQL standard states that the units after the string
242
246
specify the units of the string, e.g. INTERVAL '2' MINUTE
@@ -257,33 +261,33 @@ <h1><a name="section_4">Data Types</a></h1>
257
261
range of units supported, e.g. PostgreSQL supports '1 year 1
258
262
hour', while the SQL standard does not.
259
263
</ p >
260
- </ li > < li > Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH
261
- </ li > < li > Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS
264
+ </ li > < li > Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH
265
+ </ li > < li > Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS
262
266
INTERVAL MONTH), and this should return '12 months'
263
- </ li > < li > Round or truncate values to the requested precision, e.g.
267
+ </ li > < li > Round or truncate values to the requested precision, e.g.
264
268
INTERVAL '11 months' AS YEAR should return one or zero
265
- </ li > < li > Support precision, CREATE TABLE foo (a INTERVAL MONTH(3))
266
- </ li > </ ul >
267
- </ li > </ ul >
268
- </ li > < li > Arrays
269
+ </ li > < li > Support precision, CREATE TABLE foo (a INTERVAL MONTH(3))
269
270
< ul >
270
- < li > -< em > Allow NULLs in arrays</ em >
271
- </ li > < li > Delay resolution of array expression's data type so assignment
271
+ < li > Arrays
272
+ < ul >
273
+ < li > -< em > Allow NULLs in arrays</ em >
274
+ </ li > < li > Delay resolution of array expression's data type so assignment
272
275
coercion can be performed on empty array expressions
273
- </ li > </ ul >
274
- </ li > < li > Binary Data
275
- < ul >
276
- < li > Improve vacuum of large objects, like /contrib/vacuumlo?
277
- </ li > < li > Add security checking for large objects
278
- </ li > < li > Auto-delete large objects when referencing row is deleted
276
+ </ li > </ ul >
277
+ </ li > < li > Binary Data
278
+ < ul >
279
+ < li > Improve vacuum of large objects, like /contrib/vacuumlo?
280
+ </ li > < li > Add security checking for large objects
281
+ </ li > < li > Auto-delete large objects when referencing row is deleted
279
282
< p > /contrib/lo offers this functionality.
280
283
</ p >
281
- </ li > < li > Allow read/write into TOAST values like large objects
284
+ </ li > < li > Allow read/write into TOAST values like large objects
282
285
< p > This requires the TOAST column to be stored EXTERNAL.
283
286
</ p >
284
- </ li > < li > Add API for 64-bit large object access
287
+ </ li > < li > Add API for 64-bit large object access
285
288
< p > < a href ="http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php "> http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php</ a >
286
289
</ p >
290
+ </ li > </ ul >
287
291
</ li > </ ul >
288
292
</ li > </ ul >
289
293
< h1 > < a name ="section_5 "> Functions</ a > </ h1 >
0 commit comments