Yes alright, thanks. That's what I meant, but it's not easily replicable since you have to write specific code for any such migration.
Anyway, I understand there is no off-the-shelf easier solution, so I'll go with that for now. Thanks Michael Le ven. 10 juil. 2020 à 16:52, Jeremy Evans <[email protected]> a écrit : > On Friday, July 10, 2020 at 12:22:03 AM UTC-7, Michael Monerau wrote: >> >> Thanks Jeremy, that was also my train of thought. >> >> But I don't see an easy way in `pg_enum` to check for existing enum >> values. The only way I see would be to check the schema of an existing >> table, which is not easily replicable. >> > > If the enum is not used in any table, it should be safe to drop and > recreate. If the enum is used in any table, pick any table with the enum > and get the schema for it to look for the enum values. > > Thanks, > Jeremy > > -- > You received this message because you are subscribed to the Google Groups > "sequel-talk" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sequel-talk/f9f47b5b-4af3-40b6-8e45-92370d168113o%40googlegroups.com > <https://groups.google.com/d/msgid/sequel-talk/f9f47b5b-4af3-40b6-8e45-92370d168113o%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sequel-talk/CAAkfp_SaRAmsTYgOBmdXkQU0%3DTdbYkoJCH5PcJ7yzB_2Wvg9VA%40mail.gmail.com.
