blocks|key|1185970|text|我似乎不能发表评论，所以我只能说在Postgres8.4中更新pg_enum是可行的。对于我们的枚举的设置方式，我通过以下方式向现有的枚举类型添加了新值：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1185971|INSERT+INTO+pg_enum+(enumtypid,+enumlabel)
++SELECT+typelem,+'NEWENUM'+FROM+pg_type+WHERE
++++typname+=+'_ENUMNAME_WITH_LEADING_UNDERSCORE';|code-block|syntax|javascript|1185972|这有点吓人，但考虑到Postgres实际存储数据的方式，这是有意义的。|1185973|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I can't seem to post a comment, so I'll just say that updating pg_enum works in Postgres 8.4 . For the way our enums are set up, I've added new values to existing enum types via:

<pre><code>INSERT INTO pg_enum (enumtypid, enumlabel)
 SELECT typelem, 'NEWENUM' FROM pg_type WHERE
 typname = '_ENUMNAME_WITH_LEADING_UNDERSCORE';
</code></pre>

It's a little scary, but it makes sense given the way Postgres actually stores its data.

blocks|key|1186045|text|更新pg_enum是可行的，正如上面突出显示的中间列技巧一样。还可以使用魔法直接更改列的类型：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1186046|CREATE+TYPE+test+AS+enum('a',+'b');
CREATE+TABLE+foo+(bar+test);
INSERT+INTO+foo+VALUES+('a'),+('b');

ALTER+TABLE+foo+ALTER+COLUMN+bar+TYPE+varchar;

DROP+TYPE+test;
CREATE+TYPE+test+as+enum('a',+'b',+'c');

ALTER+TABLE+foo+ALTER+COLUMN+bar+TYPE+test
USING+CASE
WHEN+bar+=+ANY+(enum_range(null::test)::varchar[])
THEN+bar::test
WHEN+bar+=+ANY+('{convert,+these,+values}'::varchar[])
THEN+'c'::test
ELSE+NULL
END;|code-block|syntax|javascript|1186047|只要您没有显式请求或返回枚举的函数，就很好。(如果有，pgsql会在您删除该类型时发出警告。)|1186048|另外，请注意PG9.1引入了一个ALTER+TYPE语句，它将在枚举上工作：|1186049|http://developer.postgresql.org/pgdocs/postgres/release-9-1-alpha.html|offset|length|1186050|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|1Y|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|W|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|X|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|Y|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|Z|8|@]|9|@$M|10|N|11|1|12]]|A|$]]|$1|O|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|L]]]]

Updating pg_enum works, as does the intermediary column trick highlighted above. One can also use USING magic to change the column's type directly:

<pre><code>CREATE TYPE test AS enum('a', 'b');
CREATE TABLE foo (bar test);
INSERT INTO foo VALUES ('a'), ('b');

ALTER TABLE foo ALTER COLUMN bar TYPE varchar;

DROP TYPE test;
CREATE TYPE test as enum('a', 'b', 'c');

ALTER TABLE foo ALTER COLUMN bar TYPE test
USING CASE
WHEN bar = ANY (enum_range(null::test)::varchar[])
THEN bar::test
WHEN bar = ANY ('{convert, these, values}'::varchar[])
THEN 'c'::test
ELSE NULL
END;
</code></pre>

As long as you've no functions that explicitly require or return that enum, you're good. (pgsql will complain when you drop the type if there are.)

Also, note that PG9.1 is introducing an ALTER TYPE statement, which will work on enums:

<a href="http://developer.postgresql.org/pgdocs/postgres/release-9-1-alpha.html" rel="noreferrer">http://developer.postgresql.org/pgdocs/postgres/release-9-1-alpha.html</a>

blocks|key|1401492|text|使用Navicat时，您可以转到类型(在view+->+others+->+types下)-获取类型的设计视图-然后单击"add+label“按钮。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1401493|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

When using Navicat you can go to types (under view -> others -> types) - get the design view of the type - and click the "add label" button.

blocks|key|1401551|text|一种可能的解决方案如下；前提是在使用的枚举值中不存在冲突。(例如，删除枚举值时，请确保不再使用此值。)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1401552|--+rename+the+old+enum
alter+type+my_enum+rename+to+my_enum__;
--+create+the+new+enum
create+type+my_enum+as+enum+('value1',+'value2',+'value3');

--+alter+all+you+enum+columns
alter+table+my_table
++alter+column+my_column+type+my_enum+using+my_column::text::my_enum;

--+drop+the+old+enum
drop+type+my_enum__;|code-block|syntax|javascript|1401553|同样，在这种方式下，列的顺序也不会改变。|1401554|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

A possible solution is the following; precondition is, that there are not conflicts in the used enum values. (e.g. when removing an enum value, be sure that this value is not used anymore.)

<pre><code>-- rename the old enum
alter type my_enum rename to my_enum__;
-- create the new enum
create type my_enum as enum ('value1', 'value2', 'value3');

-- alter all you enum columns
alter table my_table
 alter column my_column type my_enum using my_column::text::my_enum;

-- drop the old enum
drop type my_enum__;
</code></pre>

Also in this way the column order will not be changed.

blocks|key|1186224|text|我不知道是否有其他选择，但我们可以使用以下命令删除该值：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1186225|select+oid+from+pg_type+where+typname+=+'fase';'
select+*+from+pg_enum+where+enumtypid+=+24773;'
select+*+from+pg_enum+where+enumtypid+=+24773+and+enumsortorder+=+6;
delete+from+pg_enum+where+enumtypid+=+24773+and+enumsortorder+=+6;|code-block|syntax|javascript|1186226|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I don't know if have other option but we can drop the value using:

<pre><code>select oid from pg_type where typname = 'fase';'
select * from pg_enum where enumtypid = 24773;'
select * from pg_enum where enumtypid = 24773 and enumsortorder = 6;
delete from pg_enum where enumtypid = 24773 and enumsortorder = 6;
</code></pre>

blocks|key|1186301|text|这是一个更通用但相当快速的解决方案，除了更改类型本身之外，它还使用它更新数据库中的所有列。即使新版本的ENUM有一个以上的标签不同或缺少一些原始标签，也可以应用该方法。下面的代码用ENUM+('a',+'b',+'d',+'e')替换了my_schema.my_type+AS+ENUM+('a',+'b',+'c')|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1186302|CREATE+OR+REPLACE+FUNCTION+tmp()+RETURNS+BOOLEAN+AS
$BODY$

DECLARE
++++item+RECORD;

BEGIN

++++--+1.+create+new+type+in+replacement+to+my_type
++++CREATE+TYPE+my_schema.my_type_NEW
++++++++AS+ENUM+('a',+'b',+'d',+'e');

++++--+2.+select+all+columns+in+the+db+that+have+type+my_type
++++FOR+item+IN
++++++++SELECT+table_schema,+table_name,+column_name,+udt_schema,+udt_name
++++++++++++FROM+information_schema.columns
++++++++++++WHERE
++++++++++++++++udt_schema+++=+'my_schema'
++++++++++++AND+udt_name+++++=+'my_type'
++++LOOP
++++++++--+3.+Change+the+type+of+every+column+using+my_type+to+my_type_NEW
++++++++EXECUTE
++++++++++++'+ALTER+TABLE+'+%7C%7C+item.table_schema+%7C%7C+'.'+%7C%7C+item.table_name
+++++++++%7C%7C+'+ALTER+COLUMN+'+%7C%7C+item.column_name
+++++++++%7C%7C+'+TYPE+my_schema.my_type_NEW'
+++++++++%7C%7C+'+USING+'+%7C%7C+item.column_name+%7C%7C+'::text::my_schema.my_type_NEW;';
++++END+LOOP;

++++--+4.+Delete+an+old+version+of+the+type
++++DROP+TYPE+my_schema.my_type;

++++--+5.+Remove+_NEW+suffix+from+the+new+type
++++ALTER+TYPE+my_schema.my_type_NEW
++++++++RENAME+TO+my_type;

++++RETURN+true;

END
$BODY$
LANGUAGE+'plpgsql';

SELECT+*+FROM+tmp();
DROP+FUNCTION+tmp();|code-block|syntax|javascript|1186303|整个过程将运行得相当快，因为如果标签的顺序保持不变，则不会发生实际的数据更改。我使用my_type在5个表上应用了该方法，每个表有50,000个−，70,000行，整个过程只用了10秒钟。|1186304|当然，如果在数据中使用了新版本的ENUM中缺少的标签，该函数将返回一个异常，但在这种情况下，无论如何都应该提前做一些事情。|1186305|entityMap^0|2I|P|3A|15|0|0|16|7|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|Z|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|P|$]]

Here is a more general but a rather fast-working solution, which apart from changing the type itself updates all columns in the database using it. The method can be applied even if a new version of ENUM is different by more than one label or misses some of the original ones. The code below replaces <code>my_schema.my_type AS ENUM ('a', 'b', 'c')</code> with <code>ENUM ('a', 'b', 'd', 'e')</code>:

<pre><code>CREATE OR REPLACE FUNCTION tmp() RETURNS BOOLEAN AS
$BODY$

DECLARE
 item RECORD;

BEGIN

 -- 1. create new type in replacement to my_type
 CREATE TYPE my_schema.my_type_NEW
 AS ENUM ('a', 'b', 'd', 'e');

 -- 2. select all columns in the db that have type my_type
 FOR item IN
 SELECT table_schema, table_name, column_name, udt_schema, udt_name
 FROM information_schema.columns
 WHERE
 udt_schema = 'my_schema'
 AND udt_name = 'my_type'
 LOOP
 -- 3. Change the type of every column using my_type to my_type_NEW
 EXECUTE
 ' ALTER TABLE ' || item.table_schema || '.' || item.table_name
 || ' ALTER COLUMN ' || item.column_name
 || ' TYPE my_schema.my_type_NEW'
 || ' USING ' || item.column_name || '::text::my_schema.my_type_NEW;';
 END LOOP;

 -- 4. Delete an old version of the type
 DROP TYPE my_schema.my_type;

 -- 5. Remove _NEW suffix from the new type
 ALTER TYPE my_schema.my_type_NEW
 RENAME TO my_type;

 RETURN true;

END
$BODY$
LANGUAGE 'plpgsql';

SELECT * FROM tmp();
DROP FUNCTION tmp();
</code></pre>

The whole process will run fairly quickly, because if the order of labels persists, no actual change of data will happen. I applied the method on 5 tables using <code>my_type</code> and having 50,000−70,000 rows in each, and the whole process took just 10 seconds.

Of course, the function will return an exception in case if labels that are missing in the new version of the ENUM are used somewhere in the data, but in such situation something should be done beforehand anyway.

blocks|key|1186355|text|来自postgres9.1+Documentation|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1186356|ALTER+TYPE+name+ADD+VALUE+new_enum_value+[+{+BEFORE+%7C+AFTER+}+existing_enum_value+]|code-block|syntax|javascript|1186357|示例：|1186358|ALTER+TYPE+user_status+ADD+VALUE+'PROVISIONAL'+AFTER+'NORMAL'|1186359|entityMap|0|LINK|mutability|MUTABLE|url|http://www.postgresql.org/docs/9.1/static/sql-altertype.html^0|E|D|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|10|8|@]|9|@]|C|$G|H]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

From Postgres 9.1 <a href="http://www.postgresql.org/docs/9.1/static/sql-altertype.html">Documentation</a>:

<pre><code>ALTER TYPE name ADD VALUE new_enum_value [ { BEFORE | AFTER } existing_enum_value ]
</code></pre>

Example:

<pre><code>ALTER TYPE user_status ADD VALUE 'PROVISIONAL' AFTER 'NORMAL'
</code></pre>

blocks|key|1401791|text|无法将注释添加到适当的位置，但在列上使用默认值的ALTER+TABLE+foo+ALTER+COLUMN+bar+TYPE+new_enum_type+USING+bar::text::new_enum_type失败。我不得不：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1401792|ALTER+table+ALTER+COLUMN+bar+DROP+DEFAULT；|1401793|然后它成功了。|1401794|entityMap^0|O|2A|0|0|15|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|K|$]]

Can't add a comment to the appropriate place, but <code>ALTER TABLE foo ALTER COLUMN bar TYPE new_enum_type USING bar::text::new_enum_type</code> with a default on the column failed. I had to:

<code>ALTER table ALTER COLUMN bar DROP DEFAULT</code>;

and then it worked.

blocks|key|1186480|text|补充@Dariusz+1|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1186481|对于Rails+4.2.1，有这个文档部分：|1186482|==事务性迁移|1186483|如果数据库适配器支持DDL事务，则所有迁移都将自动包装在一个事务中。但是，有些查询不能在事务内执行，对于这些情况，您可以关闭自动事务。|1186484|class+ChangeEnum+<+ActiveRecord::Migration
++disable_ddl_transaction!

++def+up
++++execute+"ALTER+TYPE+model_size+ADD+VALUE+'new_value'"
++end
end|code-block|syntax|javascript|1186485|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1771543/postgresql-updating-an-enum-type/7834949#7834949^0|B|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|11|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|C|$]]|$1|J|3|K|5|L|7|13|8|@]|9|@]|C|$M|N]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

Complementing @Dariusz <a href="https://stackoverflow.com/questions/1771543/postgresql-updating-an-enum-type/7834949#7834949">1</a>

For Rails 4.2.1, there's this doc section:

== Transactional Migrations

If the database adapter supports DDL transactions, all migrations will
 automatically be wrapped in a transaction. There are queries that you
 can't execute inside a transaction though, and for these situations
 you can turn the automatic transactions off.

<pre><code>class ChangeEnum &lt; ActiveRecord::Migration
 disable_ddl_transaction!

 def up
 execute "ALTER TYPE model_size ADD VALUE 'new_value'"
 end
end
</code></pre>

blocks|key|1186569|text|如果遇到需要在transaction中添加enum值的情况，f.e.在ALTER+TYPE语句上的flyway迁移中执行它，您将得到错误ERROR:+ALTER+TYPE+...+ADD+cannot+run+inside+a+transaction+block+(请参见flyway+issue+#350)您可以将以下值直接添加到pg_enum中作为解决方法(type_egais_units是目标enum的名称)：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1186570|INSERT+INTO+pg_enum+(enumtypid,+enumlabel,+enumsortorder)
++++SELECT+'type_egais_units'::regtype::oid,+'NEW_ENUM_VALUE',+(+SELECT+MAX(enumsortorder)+%2B+1+FROM+pg_enum+WHERE+enumtypid+=+'type_egais_units'::regtype+)|code-block|syntax|javascript|1186571|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/flyway/flyway/issues/350^0|L|4|Z|A|1W|1R|4M|7|51|G|5K|4|3S|H|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@$9|15|A|16|1|17]]|E|$]]|$1|F|3|G|5|H|7|18|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]]]

If you fall into situation when you should add <code>enum</code> values in transaction, f.e. execute it in flyway migration on <code>ALTER TYPE</code> statement you will be get error <code>ERROR: ALTER TYPE ... ADD cannot run inside a transaction block</code> (see <a href="https://github.com/flyway/flyway/issues/350" rel="noreferrer">flyway issue #350</a>) you could add such values into <code>pg_enum</code> directly as workaround (<code>type_egais_units</code> is name of target <code>enum</code>):

<pre><code>INSERT INTO pg_enum (enumtypid, enumlabel, enumsortorder)
 SELECT 'type_egais_units'::regtype::oid, 'NEW_ENUM_VALUE', ( SELECT MAX(enumsortorder) + 1 FROM pg_enum WHERE enumtypid = 'type_egais_units'::regtype )
</code></pre>

blocks|key|1186640|text|如上所述，ALTER命令不能在事务内编写。建议的方法是通过retrieving+the+typelem+from+pg_type+table和calculating+the+next+enumsortorder+number直接插入pg_enum表；|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1186641|以下是我使用的代码。(插入前检查是否存在重复值(枚举类型if和枚举标签名称之间的约束)|1186642|INSERT+INTO+pg_enum+(enumtypid,+enumlabel,+enumsortorder)
++++SELECT+typelem,
++++'NEW_ENUM_VALUE',
++++(SELECT+MAX(enumsortorder)+%2B+1+
++++++++FROM+pg_enum+e
++++++++JOIN+pg_type+p
++++++++ON+p.typelem+=+e.enumtypid
++++++++WHERE+p.typname+=+'_mytypename'
++++)
++++FROM+pg_type+p
++++WHERE+p.typname+=+'_mytypename'
++++AND+NOT+EXISTS+(
++++++++SELECT+*+FROM+
++++++++pg_enum+e
++++++++JOIN+pg_type+p
++++++++ON+p.typelem+=+e.enumtypid
++++++++WHERE+e.enumlabel+=+'NEW_ENUM_VALUE'
++++++++AND+p.typname+=+'_mytypename'
++++)|code-block|syntax|javascript|1186643|请注意，在pg_type表中，您的类型名称前面有一个下划线。此外，在where子句中，类型名需要全部小写。|1186644|现在，这可以安全地写入到您的数据库迁移脚本中。|1186645|entityMap^0|5|5|T|15|1Z|15|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|11|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|12|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|R|$]]

As discussed above, <code>ALTER</code> command cannot be written inside a transaction. The suggested way is to insert into the pg_enum table directly, by <code>retrieving the typelem from pg_type table</code> and <code>calculating the next enumsortorder number</code>;

Following is the code that I use. (Checks if duplicate value exists before inserting (constraint between enumtypid and enumlabel name)

<pre><code>INSERT INTO pg_enum (enumtypid, enumlabel, enumsortorder)
 SELECT typelem,
 'NEW_ENUM_VALUE',
 (SELECT MAX(enumsortorder) + 1 
 FROM pg_enum e
 JOIN pg_type p
 ON p.typelem = e.enumtypid
 WHERE p.typname = '_mytypename'
 )
 FROM pg_type p
 WHERE p.typname = '_mytypename'
 AND NOT EXISTS (
 SELECT * FROM 
 pg_enum e
 JOIN pg_type p
 ON p.typelem = e.enumtypid
 WHERE e.enumlabel = 'NEW_ENUM_VALUE'
 AND p.typname = '_mytypename'
 )
</code></pre>

Note that your type name is prepended with an underscore in the pg_type table. Also, the typname needs to be all lowercase in the where clause.

Now this can be written safely into your db migrate script.

blocks|key|1402094|text|以防万一，如果您使用的是Rails，并且有几个语句，则需要逐个执行，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1402095|execute+"ALTER+TYPE+XXX+ADD+VALUE+IF+NOT+EXISTS+'YYY';"
execute+"ALTER+TYPE+XXX+ADD+VALUE+IF+NOT+EXISTS+'ZZZ';"|code-block|syntax|javascript|1402096|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

just in case, if you are using Rails and you have several statements you will need to execute one by one, like:

<pre><code>execute "ALTER TYPE XXX ADD VALUE IF NOT EXISTS 'YYY';"
execute "ALTER TYPE XXX ADD VALUE IF NOT EXISTS 'ZZZ';"
</code></pre>

I have a table column that uses an <code>enum</code> type. I wish to update that <code>enum</code> type to have an additional possible value. I don't want to delete any existing values, just add the new value. What is the simplest way to do this?

Adding a new value to an existing ENUM Type

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个使用enum类型的表列。我希望更新该enum类型，使其具有一个额外的可能值。我不想删除任何现有的值，只想添加新的值。执行此操作的最简单方法是什么？

问向现有ENUM类型添加新值
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问向现有ENUM类型添加新值EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问向现有ENUM类型添加新值
EN