From: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> |
---|---|
To: | gss+pg(at)cs(dot)brown(dot)edu |
Cc: | PostgreSQL general mailing list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: transactions, serial ids, and JDBC |
Date: | 2002-08-07 22:45:37 |
Message-ID: | 87sn1qe19q.fsf@klamath.dyndns.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Gregory Seidman <gss+pg(at)cs(dot)brown(dot)edu> writes:
> I don't know how to dependably get the id from the last insert. One
> possibility, I suppose, is to call nextval myself and use the value
> explicitly, but if there is a way to do it portably (i.e. not depending on
> PostgreSQL's specific implementation of a self-incrementing id field) I
> would prefer it.
Use currval() to get the last ID produced by a sequence. AFAIK most
databases implement a concept similar to sequences, but it's not
standardized -- i.e. it will be difficult or impossible to use the
same technique with different database systems.
> Oh, one more thing. I'm doing this from JDBC. Can I do transactions with a
> long text string with all of this, or do I need to send each line
> (including BEGIN and END) as a separate Statement?
Either way will work.
Cheers,
Neil
--
Neil Conway <neilconway(at)rogers(dot)com>
PGP Key ID: DB3C29FC
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Christian Imbeault | 2002-08-07 23:01:57 | SQL statement to set next serial value to max of a table? |
Previous Message | Gregory Seidman | 2002-08-07 22:41:22 | transactions, serial ids, and JDBC |