Hi,
maybe it's a stupid question, but i do not remember how to query a table and
to request only the latest 3 added records.
How can i do that (i have a field time and a field date) ?
thx.
--
Alain
Windows XP SP3
PostgreSQL 8.2.4 / MS SQL server 2005
Apache
am Sat, dem 27.09.2008, um 9:13:48 +0200 mailte Alain Roger folgendes:
> Hi,
>
> maybe it's a stupid question, but i do not remember how to query a table and
> to
> request only the latest 3 added records.
> How can i do that (i have a field time and a field date) ?
... order by desc limit 3;
Hi,
i have a schema called : test_survey
i have within this schema this table:
CREATE TABLE test_survey.accounts
(
"ID" bigint NOT NULL DEFAULT
nextval('test_survey."accounts_ID_seq"'::regclass),
"login" character varying(300) NOT NULL,
pwd character varying(100) NOT NULL,
creation_date ti
>
> when i write the following query i get the error :ERROR:
> relation
> "accounts_id_seq" does not exist
> SET search_path = test_survey;
> insert into accounts values
> (nextval('accounts_ID_seq'),'[EMAIL
> PROTECTED]','ab4ef51934f2d3f02f1a','11/19/2007
> 15:46:09');
>
> why ?
>
It's lower
if i double-quote it, postgre tells me that the column accounts_id_seq does
not exist.
On Sat, Sep 27, 2008 at 5:59 PM, Glyn Astill <[EMAIL PROTECTED]> wrote:
> >
> > when i write the following query i get the error :ERROR:
> > relation
> > "accounts_id_seq" does not exist
> > SET search_path = t
you'll need to reference the column with the correct camel_case as
accounts_ID_seq != accounts_id_seq
hint: next time you create a table keep the table and column names lowercase
Martin
__
Disclaimer and confidentiality note
Everything in this e-mail
On Sat, Sep 27, 2008 at 10:21 AM, Alain Roger <[EMAIL PROTECTED]> wrote:
> if i double-quote it, postgre tells me that the column accounts_id_seq does
> not exist.
You almost got it. You need to doublequote to tell nextval with
capitalization correctly, then single quote that so the query planner
Tom Lane wrote:
Tommy Gildseth <[EMAIL PROTECTED]> writes:
After a bit of looking around, and with some help from the fine people
in #postgresql on freenode, I think I figured out what was going on.
The last wal archive file was 00010003009F, and after
finishing recovery, postgresql
