Skip site navigation (1) Skip section navigation (2)

Re: Is a SERIAL column a "black box", or not?

From: Hannu Krosing <hannu(at)skype(dot)net>
To: mark(at)mark(dot)mielke(dot)cc
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Is a SERIAL column a "black box", or not?
Date: 2006-04-30 10:42:37
Message-ID: 1146393757.3785.2.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-hackers
Ühel kenal päeval, L, 2006-04-29 kell 19:41, kirjutas
mark(at)mark(dot)mielke(dot)cc:
> On Sat, Apr 29, 2006 at 05:54:19PM -0400, Tom Lane wrote:
> > In short, I think there's a reasonably good case to be made for losing the
> > hidden dependency and re-adopting the viewpoint that saying SERIAL is
> > *exactly* the same as making a sequence and then making a default
> > expression that uses the sequence.  Nothing behind the curtain.
> > 
> > Comments, other opinions?
> 
> I find it user-unfriendly that I must grant select/update to the
> SERIAL, separate than from the table. I don't really see anything
> friendly about treating the object as separate.

just define nextval() as SECURITY DEFINER 

> I do see the benefits with regard to simplified implementation, and
> flexibility.
> 
> As a compromise, I could see either choice being correct. I don't
> see either direction as being both user friendly and simple.

You can be user friendly and simple only if the user wants to do simple
things, or if you can exactly predict what a user wants, else you have
to grant some power to the user, and that involves complexity or at
least a learning curve.

-------------
Hannu


In response to

Responses

pgsql-hackers by date

Next:From: Thomas HallgrenDate: 2006-04-30 10:50:23
Subject: Finding the correct type
Previous:From: Thomas HallgrenDate: 2006-04-30 10:29:08
Subject: Re: Is a SERIAL column a "black box", or not?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group