Commit 4f81337d authored by Bruce Momjian's avatar Bruce Momjian

Update packages:

< 		  A package would be a schema with public/private variables,
> 		  A package would be a schema with session-local variables,
> 		  http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
parent e6e61afe
...@@ -2,7 +2,7 @@ ...@@ -2,7 +2,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
Last updated: Tue Aug 8 22:48:04 EDT 2006 Last updated: Wed Aug 9 10:55:32 EDT 2006
The most recent version of this document can be viewed at The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. http://www.postgresql.org/docs/faqs.TODO.html.
...@@ -689,11 +689,12 @@ SQL Commands ...@@ -689,11 +689,12 @@ SQL Commands
get_employee_salary(12345 AS emp_id, 2001 AS tax_year) get_employee_salary(12345 AS emp_id, 2001 AS tax_year)
o Add Oracle-style packages (Pavel) o Add Oracle-style packages (Pavel)
A package would be a schema with public/private variables, A package would be a schema with session-local variables,
public/private functions, and initialization functions. It public/private functions, and initialization functions. It
is also possible to implement these capabilities is also possible to implement these capabilities
in all schemas and not use a separate "packages" in all schemas and not use a separate "packages"
syntax at all. syntax at all.
http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
o Allow handling of %TYPE arrays, e.g. tab.col%TYPE[] o Allow handling of %TYPE arrays, e.g. tab.col%TYPE[]
o Allow listing of record column names, and access to o Allow listing of record column names, and access to
......
...@@ -8,7 +8,7 @@ ...@@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1> <h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/> <p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
Last updated: Tue Aug 8 22:48:04 EDT 2006 Last updated: Wed Aug 9 10:55:32 EDT 2006
</p> </p>
<p>The most recent version of this document can be viewed at<br/> <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>. <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
...@@ -623,11 +623,12 @@ first. ...@@ -623,11 +623,12 @@ first.
</li><li>Allow function parameters to be passed by name, </li><li>Allow function parameters to be passed by name,
get_employee_salary(12345 AS emp_id, 2001 AS tax_year) get_employee_salary(12345 AS emp_id, 2001 AS tax_year)
</li><li>Add Oracle-style packages (Pavel) </li><li>Add Oracle-style packages (Pavel)
<p> A package would be a schema with public/private variables, <p> A package would be a schema with session-local variables,
public/private functions, and initialization functions. It public/private functions, and initialization functions. It
is also possible to implement these capabilities is also possible to implement these capabilities
in all schemas and not use a separate "packages" in all schemas and not use a separate "packages"
syntax at all. syntax at all.
<a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php</a>
</p> </p>
</li><li>Allow handling of %TYPE arrays, e.g. tab.col%TYPE[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?"></a>] </li><li>Allow handling of %TYPE arrays, e.g. tab.col%TYPE[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?"></a>]
</li><li>Allow listing of record column names, and access to </li><li>Allow listing of record column names, and access to
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment