From: | "Serguei Mokhov" <sa_mokho(at)alcor(dot)concordia(dot)ca> |
---|---|
To: | "Bill Studenmund" <wrstuden(at)netbsd(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: namespaces |
Date: | 2001-10-20 16:29:36 |
Message-ID: | 03a701c15985$694904c0$5dd9fea9@gunn |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
----- Original Message -----
From: Bill Studenmund <wrstuden(at)netbsd(dot)org>
Sent: Sunday, October 14, 2001 8:22 AM
> My description of namespaces seems to have caused a fair bit of confusion.
> Let me try again.
>
> The ability of the package changes to automatically check standard when
> you give an ambiguous function name while in a package context is a
> convenience for the procedure author. Nothing more.
>
> It means that when you want to use one of the built in functions
> (date_part, abs, floor, sqrt etc.) you don't have to prefix it with
> "standard.". You can just say date_part(), abs(), floor(), sqrt(), etc.
> The only time you need to prefix a call with "standard." is if you want to
> exclude any so-named routines in your own package.
Quick question: would it be possible then create a 'system' package
and 'system' (or 'master' if you will) schema (when it's implemented),
move over all the system tables (pg_*) into the master schema
and functions into the 'system' package, so that no name conflicts will arise
when creating types, functions, tables, etc with the same names as system ones?
--
S.
From | Date | Subject | |
---|---|---|---|
Next Message | Ron de Jong | 2001-10-20 16:31:49 | Typhoon-Web-DataBase-Administrator-1.3.0 with PostgreSQL support released!!! |
Previous Message | Ron de Jong | 2001-10-20 16:02:31 | Re: Is there no "DESCRIBE <TABLE>;" on PGSQL? help!!! |