RE: Using curr_val Wisely

From: "Andrew Snow" <als(at)fl(dot)net(dot)au>
To: "Jeff Waugh" <jdub(at)aphid(dot)net>
Cc: "Pgsql-General(at)Postgresql(dot) Org" <pgsql-general(at)postgresql(dot)org>
Subject: RE: Using curr_val Wisely
Date: 2000-07-12 13:03:17
Message-ID: NHEALMDKDACEIPBNOOOCEEICCHAA.als@fl.net.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> I'm using curr_val('blah_id_seq') in a transaction like so: (in
> pseudo SQL)

curr_val() returns the current value of the sequence, in the current
transaction.
So an insertion in transaction A won't affect the value of it in existing
transaction B.

Regards,

Andrew

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Philip Warner 2000-07-12 13:51:13 pg_dump & blobs - editable dump?
Previous Message Sean Weissensee 2000-07-12 11:43:52 Re: PostgreSQL and Access (via ODBC)