Re: sql window issues
От | Antoine |
---|---|
Тема | Re: sql window issues |
Дата | |
Msg-id | 92d3a4950604090338y5bae94ax69d26257e98ff872@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: sql window issues ("Dave Page" <dpage@vale-housing.co.uk>) |
Список | pgadmin-support |
> Well the error comes from PostgreSQL, not pgAdmin - and now you mention you are using EXPLAIN ANALYZE it all makes sense.EXPLAINing a CREATE TABLE is pointless and unsupported by PostgreSQL. You will get the same error from psql. > > If you want to test one or more queries before executing them for real, try something like: > > BEGIN; > > 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"; > > ROLLBACK; > > Then when you're happy, just change the ROLLBACK to COMMIT. > > Regards, Dave. > I thought it had to be something silly like that - thanks for the advice! Cheers Antoine ps. I remember using a db frontend that had a syntax check function (sql server 2000 query analyser?) - that is what I have been using the explain analyse for I guess... could that be a functionality others might be interested in? -- This is where I should put some witty comment.
В списке pgadmin-support по дате отправления: