Re: sql window issues

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Antoine" <melser(dot)anton(at)gmail(dot)com>
Cc: <pgadmin-support(at)postgresql(dot)org>
Subject: Re: sql window issues
Date: 2006-04-07 08:25:29
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4011C9B20@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

> -----Original Message-----
> From: Antoine [mailto:melser(dot)anton(at)gmail(dot)com]
> Sent: 07 April 2006 08:54
> To: Dave Page
> Cc: pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] sql window issues
>
> Here is a typical error:
>
> CREATE TABLE etape
> (
> n_etp_code numeric(6) NOT NULL, -- identifiant de la table
> t_etp_intitule varchar(50), -- nom en clair de l'étape
> CONSTRAINT pk_etape PRIMARY KEY (n_etp_code)
> )
> WITHOUT OIDS;
> ALTER TABLE etape OWNER TO "PRODUCTION";
>
>
> La requête a inséré une ligne d'OID 0.
>
> ERROR: syntax error at or near "numeric" at character 45
>
> Could it be an encoding issue? That pgadmin doesn't like code
> from a copy paste?

The code above works fine for me, copied'n'pasted from your email:

NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "pk_etape" for table "etape"

Query returned successfully with no result in 313 ms.

What does: La requête a inséré une ligne d'OID 0. mean?

Regards, Dave

Browse pgadmin-support by date

  From Date Subject
Next Message Dave Page 2006-04-08 15:11:19 Re: sql window issues
Previous Message Antoine 2006-04-07 07:53:50 Re: sql window issues