pgsql: Update wording, query -> statement: < * %Allow pooled

Поиск
Список
Период
Сортировка
От momjian@postgresql.org (Bruce Momjian)
Тема pgsql: Update wording, query -> statement: < * %Allow pooled
Дата
Msg-id 20051212133637.1F46A9DD076@postgresql.org
обсуждение исходный текст
Список pgsql-committers
Log Message:
-----------
Update wording, query -> statement:

< * %Allow pooled connections to list all prepared queries
> * %Allow pooled connections to list all prepared statements
28c28
<   the queries prepared in the current session.
>   the statements prepared in the current session.
143c143
<       o Allow a warm standby system to also allow read-only queries
>       o Allow a warm standby system to also allow read-only statements
404c404
< * Add GUC to issue notice about queries that use unjoined tables
> * Add GUC to issue notice about statements that use unjoined tables
490c490
<       Another idea would be to allow actual SELECT queries in a COPY.
>       Another idea would be to allow actual SELECT statements in a COPY.
554c554
<     o Allow function argument names to be queries from PL/PgSQL
>     o Allow function argument names to be statements from PL/PgSQL
591c591
<     o Improve psql's handling of multi-line queries
>     o Improve psql's handling of multi-line statements
<       Currently, while \e saves a single query as one entry, interactive
<       queries are saved one line at a time.  Ideally all queries
>       Currently, while \e saves a single statement as one entry, interactive
>       statements are saved one line at a time.  Ideally all statements
665c665
<     o Allow query results to be automatically batched to the client
>     o Allow statement results to be automatically batched to the client
667c667
<       Currently, all query results are transfered to the libpq
>       Currently, all statement results are transfered to the libpq
672c672
<       One complexity is that a query like SELECT 1/col could error
>       One complexity is that a statement like SELECT 1/col could error
739c739
< * Allow queries across databases or servers with transaction
> * Allow statements across databases or servers with transaction
<   inheritance, allow it to work for UPDATE and DELETE queries, and allow
<   it to be used for all queries with little performance impact
>   inheritance, allow it to work for UPDATE and DELETE statements, and allow
>   it to be used for all statements with little performance impact
876c876
< * Consider automatic caching of queries at various levels:
> * Consider automatic caching of statements at various levels:
947c947
<   a single session using multiple threads to execute a query faster.
>   a single session using multiple threads to execute a statement faster.
1025c1025
< * Log queries where the optimizer row estimates were dramatically
> * Log statements where the optimizer row estimates were dramatically
1146c1146
<       of result sets using new query protocol
>       of result sets using new statement protocol

Modified Files:
--------------
    pgsql/doc:
        TODO (r1.1724 -> r1.1725)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1724&r2=1.1725)
    pgsql/doc/src/FAQ:
        TODO.html (r1.230 -> r1.231)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.230&r2=1.231)

В списке pgsql-committers по дате отправления:

Предыдущее
От: swm@pgfoundry.org (User Swm)
Дата:
Сообщение: mysqlcompat - mysqlcompat: Implement make_set().
Следующее
От: sven@pgfoundry.org (User Sven)
Дата:
Сообщение: wikipedia - wikipgedia: Generate passwords long enough for