Re: problem inserting with sequence - Mailing list pgsql-general

From germ germ
Subject Re: problem inserting with sequence
Date
Msg-id 20050728140455.17792.qmail@web53408.mail.yahoo.com
Whole thread Raw
In response to Re: problem inserting with sequence  (Michael Fuhr <mike@fuhr.org>)
Responses Re: problem inserting with sequence
Re: problem inserting with sequence
Re: problem inserting with sequence
List pgsql-general
This is the error: 2005-07-28 08:51:08 ERROR:
permission denied for sequence requests_req_num_seq

I've tried these grants, but no luck:
GRANT ALL ON FUNCTION nextval(integer) TO wwwrun,
postgres;
GRANT ALL ON FUNCTION nextval('requests_req_num_seq')
TO wwwrun, postgres;
GRANT ALL ON FUNCTION nextval() TO wwwrun, postgres;

--- Michael Fuhr <mike@fuhr.org> wrote:

> On Thu, Jul 28, 2005 at 05:32:03AM -0700, germ germ
> wrote:
> > I have been trying to figure out why I can't
> insert
> > into a table and I think it has something to do
> with
> > the sequnce.
> >
> > I am able to use able to properly insert into the
> > table using the the shell, but I am not able to
> insert
> > using a php script:
> >
> > INSERT INTO requests (time_stamp, req_num,
> > recommended_by) VALUES (now(),
> > nextval('requests_req_num_seq'), 'foo');
>
> What happens when you try the insert?  We need more
> details than
> just "it doesn't work."  If there's an error then it
> should be in
> the postmaster logs, and it should also be available
> to the PHP
> script.
>
> What's different between the situation that works
> and the one that
> doesn't?  Are you connecting as different users?  In
> the code you
> posted I don't see any permissions being granted on
> the sequence,
> so nextval() might be failing with "permission
> denied for sequence";
> another possibility is that the sequence name is
> wrong (see below).
>
> > Here is the schema I'm using:
> > DROP SEQUENCE requests_req_num_seq;
> > DROP TABLE requests;
> >
> > CREATE SEQUENCE requests_req_num_seq INCREMENT BY
> 1
> > START WITH 1000;
> >
> > CREATE TABLE requests (
> >     time_stamp         timestamp    PRIMARY KEY DEFAULT 'now',
>
>
> A timestamp is a poor choice for a primary key
> because it's not
> unique; aside from that you've defined the default
> to be a constant --
> run "\d requests" in psql and you'll see what I
> mean.  See the
> following section of the documentation for more
> info:
>
>
http://www.postgresql.org/docs/7.4/static/functions-datetime.html#FUNCTIONS-DATETIME-CURRENT
>
> >     req_num            integer        DEFAULT
> > nextval('acq_requests_req_num_seq') NOT NULL,
>
> This sequence name doesn't match the name of the
> sequence you created,
> at least not the one you showed.  Is there an
> acq_requests_req_num_seq
> sequence?
>
> --
> Michael Fuhr
> http://www.fuhr.org/~mfuhr/
>




____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs


pgsql-general by date:

Previous
From: Paul Tillotson
Date:
Subject: Re: duplicate messages?
Next
From: david.best@sympatico.ca
Date:
Subject: Perl DBI and postgres