On Wed, Jan 8, 2014 at 1:24 PM, David Johnston <polobo@xxxxxxxxx> wrote:
Yeah, default timestamp was the best solution I could come up with, but I
was hoping there was a way to access the actual PK of the most recent insert.
Looks like timestamp it is.
Thanks everyone!
Nelson Green wrote
> My apologies, I was not completely clear. I will not know any of theI'd probably add either (or both) a table-level auto-sequence field and a
> columns in advance. The most recent insert is the result of user input
> from
> a web form, so I won't know what project or what user generated the last
> insert. That was why I wandered if that information was stored anywhere in
> the system.
"recordcreationdate" default timestamptz field.
Yeah, default timestamp was the best solution I could come up with, but I
was hoping there was a way to access the actual PK of the most recent insert.
Looks like timestamp it is.
Thanks everyone!
David J.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Last-inserted-row-id-with-complex-PK-tp5785863p5785901.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
