Re: ALTER TABLE follow up
От | Christopher Kings-Lynne |
---|---|
Тема | Re: ALTER TABLE follow up |
Дата | |
Msg-id | GNELIHDDFBOCMGBFGEFOCEIPCDAA.chriskl@familyhealth.com.au обсуждение исходный текст |
Ответ на | ALTER TABLE follow up ("Tom Haddon" <tom@betterhealthfoundation.org>) |
Ответы |
Re: ALTER TABLE follow up
|
Список | pgsql-sql |
Hi Tom, > A follow up to the ALTER TABLE question last week. I had asked why I was > getting an error message using the ALTER TABLE to add a PRIMARY > KEY, and was > told that this wasn't supported in 7.1.x. I've upgraded to 7.2.1 and now > when I use the following SQL: > > ALTER TABLE "agency_contact_info" ADD CONSTRAINT > "agency_contact_info_pkey" > PRIMARY KEY NOT NULL ("id"); I have no idea where you got that NOT NULL bit from - it's not in the manual. In fact Posgres 7.2 has no sql function for changing the null status of a column. You can manually twiddle the catalogs however - make SURE there's no NULL values in the column first: UPDATE pg_attribute SET attnotnull = true WHERE attrelid = (SELECT oid FROM pg_class WHERE relname = 'agency_contact_info') AND attname = 'id'; Now just go: ALTER TABLE agency_contact_info ADD PRIMARY KEY (id): Chris
В списке pgsql-sql по дате отправления: