| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> | 
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: Suggestions please: names for function cachabilityattributes | 
| Date: | 2002-04-13 06:33:51 | 
| Message-ID: | Pine.LNX.4.30.0204130222420.847-100000@peter.localdomain | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general pgsql-hackers | 
Tom Lane writes:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Tom Lane writes:
> >> case 1: "immutable"
> >> case 2: "mutable", or perhaps "stable"
> >> case 3: "volatile"
>
> > Since they've changed anyway, how about dropping the silly "is" in front
> > of the names?
>
> "volatile" would conflict with a C keyword.  Possibly we could get away
> with this at the SQL level, but I was worried...
In general, I was thinking about migrating the CREATE FUNCTION syntax more
into consistency with other commmands and with the SQL standard.
Basically I'd like to write
    CREATE FUNCTION name (args, ...) RETURNS type
      AS '...'
      LANGUAGE foo
      STATIC
      IMPLICIT CAST
(where everything after RETURNS can be in random order).
OK, so the key words are not the same as SQL, but it looks a lot
friendlier this way.  We're already migrating CREATE DATABASE, I think,
and the names of the options have changed, too, so this might be a good
time.
-- 
Peter Eisentraut   peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ole | 2002-04-13 09:39:35 | Please - postgresql cannot connect? | 
| Previous Message | Ed Loehr | 2002-04-13 06:22:05 | Defn of pg_class.reltuples in 7.2.1? | 
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2002-04-13 13:32:38 | Re: 7.3 schedule | 
| Previous Message | Christopher Kings-Lynne | 2002-04-13 06:31:35 | Re: numeric/decimal docs bug? |