On Wednesday 17 January 2007 09:54, Brant Fitzsimmons wrote:
> Sean Davis wrote:
> > On Wednesday 17 January 2007 03:06, Brant Fitzsimmons wrote:
> >> Jasbinder Singh Bali wrote:
> >>> Please attach a snippet of your python script and lets see what
> >>> are you doing there. That might make things easy. Jas
> >>
> >> Here is the entire test script:
> >>
> >> #!/usr/bin/python
> >>
> >> # import pgdb module import pgdb
> >>
> >> # connect to the db db = pgdb.connect(host="localhost",
> >> database="test", user="postgres", password="**********")
> >>
> >> # instantiate cursor cursor = db.cursor()
> >>
> >> # insert 10 records for x in range(10): cursor.execute("INSERT
> >> INTO users (username, firstname, lastname, email, age) VALUES
> >> ('brant', 'Brant', 'Fitzsimmons',
> >> 'brant@bfcomputerconsulting.com', 31)")
> >
> > Put in a db.commit() statement here. Does that fix your problem?
>
> It sure does. Any idea why it would drive up the serial column even
> though nothing was committed?
Great to hear....
A serial column is a macro to make a sequence and then to fill the column with
the default "next_val" from the sequence. The mere selection of next_val
increases the sequence, which is necessary to ensure that all connections get
a unique value when selecting from the same sequence.
Sean
