mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update packages description:

Browse Source 
< 		  A package would be a schema with its own variables,
< 		  private functions, and initialization functions.  It
> 		  A package would be a schema with public/private variables,
> 		  public/private functions, and initialization functions.  It
This commit is contained in:
Bruce Momjian 2006-08-09 02:48:10 +00:00
parent bed7d5f635
commit baefb735ff
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/TODO
View File

@ -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 18:51:31 EDT 2006 Last updated: Tue Aug 8 22:48:04 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,8 +689,8 @@ 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 its own variables, A package would be a schema with public/private variables,
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.

6
doc/src/FAQ/TODO.html
View File

@ -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 18:51:31 EDT 2006 Last updated: Tue Aug 8 22:48:04 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,8 +623,8 @@ 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 its own variables, <p> A package would be a schema with public/private variables,
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.