| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: A different approach to extension NO USER DATA feature |
| Date: | 2011-02-07 14:50:09 |
| Message-ID: | AANLkTiknqAc-nug4-HHNRurgH3LouUOLPYLTaejwjd+o@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Feb 7, 2011 at 4:18 AM, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> wrote:
> Or do you want to keep some generality here?
I think it might be slightly advantageous to keep some generality,
because some people might already have catalog columns that do this
(but with a different name) or might have other reasons for needing an
integer "entry type" column from which the system property can be
inferred. I can't think how many times I've written a web interface
that lets users edit a foo, but denies them the ability to edit any
foo where bar_id = 1 (because those are the magic ones that get
created some other way).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2011-02-07 14:54:46 | Re: [COMMITTERS] pgsql: remove tags. |
| Previous Message | strk | 2011-02-07 14:38:59 | Re: DROP SCHEMA xxx CASCADE: ERROR: could not open relation with OID yyy |