From: | Francisco Leovey <fleovey(at)yahoo(dot)com> |
---|---|
To: | postgresql novice <pgsql-novice(at)postgresql(dot)org>, Luiz Eduardo Cantanhede Neri <lecneri(at)gmail(dot)com> |
Subject: | Re: Getting The Last Entry |
Date: | 2010-09-10 17:12:53 |
Message-ID: | 944030.64009.qm@web51703.mail.re2.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
It may be poor design to use OID, but have you ever tried to use a SERIAL field instead?
That alternative is a really poor choice, many headaches when you try to move data to other tables or recover a backup. There is a temptation to use the value in the SERIAL field but it is totaly useless in most cases. Duplicate values, etc.
--- On Fri, 9/10/10, Luiz Eduardo Cantanhede Neri <lecneri(at)gmail(dot)com> wrote:
From: Luiz Eduardo Cantanhede Neri <lecneri(at)gmail(dot)com>
Subject: Re: [NOVICE] Getting The Last Entry
To: "postgresql novice" <pgsql-novice(at)postgresql(dot)org>
Date: Friday, September 10, 2010, 12:49 PM
Once I suggested to use oid, but some guys here said was a poor design.
On Fri, Sep 10, 2010 at 12:33 PM, Thom Brown <thom(at)linux(dot)com> wrote:
On 10 September 2010 16:31, Francisco Leovey <fleovey(at)yahoo(dot)com> wrote:
>
> if by "last" you mean the last row inserted, use
>
> select *,oid from table order by oid DESC limit 1
>
> (asuming you use OID's)
(copying in list with your response)
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
--
Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-novice
From | Date | Subject | |
---|---|---|---|
Next Message | J. Roeleveld | 2010-09-10 17:35:13 | Re: PostgreSQL article online - PDF |
Previous Message | Luiz Eduardo Cantanhede Neri | 2010-09-10 15:49:17 | Re: Getting The Last Entry |