Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 9f6ed2f

Browse files
bmomjianbmomjian
committed
Update wording:
< Currently, ALTER USER and ALTER DATABASE support per-user and > Currently ALTER USER and ALTER DATABASE support per-user and < Currently, subtracting one date from another that crosses a > Currently subtracting one date from another that crosses a < Currently, SQL-language functions can only refer to parameters via $1, etc > Currently SQL-language functions can only refer to dollar parameters, > e.g. $1 < Currently, queries prepared via the libpq API are planned on first > Currently queries prepared via the libpq API are planned on first < Currently, SET <tab> causes a database lookup to check all > Currently SET <tab> causes a database lookup to check all < Currently, all statement results are transferred to the libpq > Currently all statement results are transferred to the libpq
1 parent 0e461f2 commit 9f6ed2f

File tree

2 files changed

+16
-14
lines changed

2 files changed

+16
-14
lines changed

‎doc/TODO

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
PostgreSQL TODO List
33
====================
44
Current maintainer: Bruce Momjian (bruce@momjian.us)
5-
Last updated: Sat Feb 17 20:32:39 EST 2007
5+
Last updated: Sat Feb 17 20:34:28 EST 2007
66

77
The most recent version of this document can be viewed at
88
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -66,7 +66,7 @@ Administration
6666
* Allow auto-selection of partitioned tables for min/max() operations
6767
* Allow more complex user/database default GUC settings
6868

69-
Currently, ALTER USER and ALTER DATABASE support per-user and
69+
Currently ALTER USER and ALTER DATABASE support per-user and
7070
per-database defaults. Consider adding per-user-and-database
7171
defaults so things like search_path can be defaulted for a
7272
specific user connecting to a specific database.
@@ -249,7 +249,7 @@ Data Types
249249
format
250250
o Improve timestamptz subtraction to be DST-aware
251251

252-
Currently, subtracting one date from another that crosses a
252+
Currently subtracting one date from another that crosses a
253253
daylight savings time adjustment can return '1 day 1 hour', but
254254
adding that back to the first date returns a time one hour in
255255
the future. This is caused by the adjustment of '25 hours' to
@@ -369,7 +369,8 @@ Functions
369369

370370
* Allow SQL-language functions to reference parameters by parameter name
371371

372-
Currently, SQL-language functions can only refer to parameters via $1, etc
372+
Currently SQL-language functions can only refer to dollar parameters,
373+
e.g. $1
373374

374375
* Add SPI_gettypmod() to return the typemod for a TupleDesc
375376
* Enforce typmod for function inputs, function results and parameters for
@@ -459,7 +460,7 @@ SQL Commands
459460
* Allow PREPARE of cursors
460461
* Allow finer control over the caching of prepared query plans
461462

462-
Currently, queries prepared via the libpq API are planned on first
463+
Currently queries prepared via the libpq API are planned on first
463464
execute using the supplied parameters --- allow SQL PREPARE to do the
464465
same. Also, allow control over replanning prepared queries either
465466
manually or automatically when statistics for execute parameters
@@ -802,7 +803,7 @@ Clients
802803
database and therefore preventing the transaction isolation
803804
level from being set.
804805

805-
Currently, SET <tab> causes a database lookup to check all
806+
Currently SET <tab> causes a database lookup to check all
806807
supported session variables. This query causes problems
807808
because setting the transaction isolation level must be the
808809
first statement of a transaction.
@@ -869,7 +870,7 @@ Clients
869870

870871
o Allow statement results to be automatically batched to the client
871872

872-
Currently, all statement results are transferred to the libpq
873+
Currently all statement results are transferred to the libpq
873874
client before libpq makes the results available to the
874875
application. This feature would allow the application to make
875876
use of the first result rows while the rest are transferred, or

‎doc/src/FAQ/TODO.html

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
99
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
1010
<p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
11-
Last updated: Sat Feb 17 20:32:39 EST 2007
11+
Last updated: Sat Feb 17 20:34:28 EST 2007
1212
</p>
1313
<p>The most recent version of this document can be viewed at<br/>
1414
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@@ -65,7 +65,7 @@ <h1><a name="section_2">Administration</a></h1>
6565
</p>
6666
</li><li>Allow auto-selection of partitioned tables for min/max() operations
6767
</li><li>Allow more complex user/database default GUC settings
68-
<p> Currently, ALTER USER and ALTER DATABASE support per-user and
68+
<p> Currently ALTER USER and ALTER DATABASE support per-user and
6969
per-database defaults. Consider adding per-user-and-database
7070
defaults so things like search_path can be defaulted for a
7171
specific user connecting to a specific database.
@@ -224,7 +224,7 @@ <h1><a name="section_4">Data Types</a></h1>
224224
</li><li>Add a GUC variable to allow output of interval values in ISO8601
225225
format
226226
</li><li>Improve timestamptz subtraction to be DST-aware
227-
<p> Currently, subtracting one date from another that crosses a
227+
<p> Currently subtracting one date from another that crosses a
228228
daylight savings time adjustment can return '1 day 1 hour', but
229229
adding that back to the first date returns a time one hour in
230230
the future. This is caused by the adjustment of '25 hours' to
@@ -337,7 +337,8 @@ <h1><a name="section_5">Functions</a></h1>
337337
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-10/msg00665.php">http://archives.postgresql.org/pgsql-hackers/2006-10/msg00665.php</a>
338338
</p>
339339
</li><li>Allow SQL-language functions to reference parameters by parameter name
340-
<p> Currently, SQL-language functions can only refer to parameters via $1, etc
340+
<p> Currently SQL-language functions can only refer to dollar parameters,
341+
e.g. $1
341342
</p>
342343
</li><li>Add SPI_gettypmod() to return the typemod for a TupleDesc
343344
</li><li>Enforce typmod for function inputs, function results and parameters for
@@ -414,7 +415,7 @@ <h1><a name="section_8">SQL Commands</a></h1>
414415
</p>
415416
</li><li>Allow PREPARE of cursors
416417
</li><li>Allow finer control over the caching of prepared query plans
417-
<p> Currently, queries prepared via the libpq API are planned on first
418+
<p> Currently queries prepared via the libpq API are planned on first
418419
execute using the supplied parameters --- allow SQL PREPARE to do the
419420
same. Also, allow control over replanning prepared queries either
420421
manually or automatically when statistics for execute parameters
@@ -719,7 +720,7 @@ <h1><a name="section_9">Clients</a></h1>
719720
</li><li>Prevent tab completion of SET TRANSACTION from querying the
720721
database and therefore preventing the transaction isolation
721722
level from being set.
722-
<p> Currently, SET &lt;tab&gt; causes a database lookup to check all
723+
<p> Currently SET &lt;tab&gt; causes a database lookup to check all
723724
supported session variables. This query causes problems
724725
because setting the transaction isolation level must be the
725726
first statement of a transaction.
@@ -779,7 +780,7 @@ <h1><a name="section_9">Clients</a></h1>
779780
historically it has so we need a way to prevent it
780781
</p>
781782
</li><li>Allow statement results to be automatically batched to the client
782-
<p> Currently, all statement results are transferred to the libpq
783+
<p> Currently all statement results are transferred to the libpq
783784
client before libpq makes the results available to the
784785
application. This feature would allow the application to make
785786
use of the first result rows while the rest are transferred, or

0 commit comments

Comments
 (0)