Re: Last ID Problem

From: <operationsengineer1(at)yahoo(dot)com>
To: Mitch Pirtle <mitch(dot)pirtle(at)gmail(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Last ID Problem
Date: 2005-05-04 16:21:52
Message-ID: 20050504162152.34287.qmail@web52405.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

> Why not first get the current value from the
> sequence, use it for your
> INSERT statement, and then have it handy for the
> rest of the script?

i hate to revisit this old topic, however, i just want
to make sure i'm avoiding future problems.

if i pull nextval then insert it into the id column
where i pulled it from, will the counter ever get "off
track" since i'm doing manual inserts?

can nextval ever become a value that's unexpected? in
practice, this method is working very well, but i'm
paranoid. ;-)

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Bruno Wolff III 2005-05-04 16:56:26 Re: Last ID Problem
Previous Message operationsengineer1 2005-05-04 16:12:40 Cascade Delete To Override Table Restrict Delete