Skip site navigation (1) Skip section navigation (2)

Re: Reverse engeenered SQL for COMMENT ON CHECK

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Luc ROLLAND" <luc(at)rolland-fr(dot)com>,<pgadmin-support(at)postgresql(dot)org>
Subject: Re: Reverse engeenered SQL for COMMENT ON CHECK
Date: 2004-02-23 11:55:05
Message-ID: 03AF4E498C591348A42FC93DEA9661B889F45C@mail.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgadmin-support
Hi Luc,
 
Thanks for the bug report - this has now been fixed in CVs and will
appear in future releases.
 
Regards, Dave.


  _____  

	From: Luc ROLLAND [mailto:luc(at)rolland-fr(dot)com] 
	Sent: 21 February 2004 10:01
	To: pgadmin-support(at)postgresql(dot)org
	Subject: [pgadmin-support] Reverse engeenered SQL for COMMENT ON
CHECK
	
	
	Hello !
	 
	First of all I use PgAdmin III and I like it !
	Actually I use :
	- PostgreSQL 7.4  v7.4.1 on Linux Mandrake 9.2 server,
	- PgAdmin III v1.0.2 on an Windows XP SP1,
	- All my systems and applications are French localized.
	 
	When on a onstraint with a comment, PgAdmin gives for ex. :
	COMMENT ON CHECK public.adressesliv_nomliv IS 'Le nom est
obligatoire';
	and I obtain
	ERROR:  syntax error at or near "CHECK" at character 12
	
	I must use :
	COMMENT ON CONSTRAINT adressesliv_nomliv ON public.adressesliv
IS 'Le nom est obligatoire';
	the CHECK keyword is not recognized.
	 
	Best regards.
	 
	Luc ROLLAND

pgadmin-support by date

Next:From: blacknozDate: 2004-02-23 14:47:13
Subject: Re: compiling problem
Previous:From: blacknozDate: 2004-02-23 11:31:10
Subject: Re: compiling problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group