request for enhancement of protocol

From: "Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: request for enhancement of protocol
Date: 2005-11-19 10:07:58
Message-ID: BAY20-F10393B8AE1CF7C3E57E6FAF9510@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello

Meybe is time for some changes. Maybe. I haven't courage for it. But maybe
is good time for discussion. What I miss in protocol?

1. debug. support + other level for elog. Current elog is too heavy
(sometimes)
2. multi result sets. This is necessery for support procedures in DB2,
MySQL, "ANSI", MsSQL style.
3. session (package) variables and calling procedures with OUT, INOUT in
normal style, tj. stmt CALL. - heavy task, because I can write function a(IN
int, IN int), and a(OUT int, OUT int) now. This is problem, and need
restriction.
4. ping

What is my motivation for 2?
1. I can write "solution" - stored application. Example: info about
growing of database. Output is n tables: first table is info about database,
others about top n - 1 tables, ...
2. easy reporting. I haven't possibility write stored procedure for
generating cross table now. I have to do all in two steps (example):
generate view, select from view. This is difference between procedures and
functions. Function have to have exactly defined interface. Procedures
can't.
3. easy porting from databases which support this style.

sorry for my wrong english.

best regards
Pavel Stehule

_________________________________________________________________
Citite se osamele? Poznejte nekoho vyjmecneho diky Match.com.
http://www.msn.cz/

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2005-11-19 10:35:55 Re: request for enhancement of protocol
Previous Message Heikki Linnakangas 2005-11-19 09:49:53 Materialized views (Was Re: Improving count(*))