On Fri, Feb 16, 2018 at 7:41 AM, <[email protected]> wrote: > We have a fairly common forwards-compatibility scenario that makes using > enums problematic: loading unknown enum values results in an exception > during loading.
I'm not entirely clear on your environment and deployment strategy. So I'll take a guess: 1. There is no change to the database structure; 2. There is a new entry in some Java enum in the "future" application; 3. Loading a record generated by the "future" application in a "current/old" application will fail to translate to the correct enum entry as it does not exist in the "current/old" application. If I am correct then it might be possible to avoid the whole problem by breaking it up: 1. Add the new enum entry to the application; 2. Deploy the application with the new enum entry added (but nothing uses it yet); 3. Add the functionality that uses the new enum entry; 4. Deploy the full "future" application. Would that work for you? -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
