Find and replace already fills the role of transforming enum values in tables. In certain enterprise databases, using enums is a really common pattern. As a result, I often need to type the same enum as a find and replace across 10-12 different datasets. While it's true I can go back and copy/paste the values, it'd be great if I could just save them with a name, then optionally indicate when another column in a different dataset follows the same enum to automatically transform it. That way, if I need to edit the enum, I can edit it in one place, and transforming the enum from numbers to meaningful values becomes just a couple keystrokes.
Additionally, in certain databases, there are builtin functions to look up enum maps. For example, in Oracle, xform_enum() is available.For databases where such features are available, it'd be great to save the effort entirely and just type the name of the enum without ever typing the mapping. Alternatively, perhaps an enum column meaning could provide similar functionality.with the added benefit of generating local context menus prompting users to quickly assign the correct enum and convert automatically.Some enums in my company are quite large (50+ mapped values), so being able to lookup those values from the database would be a big time saver.