This post is simply a log of Berkeley DB burns or gotchas written as rules to be remembered. The post will be updated as time goes by.
1. Don’t just change your enum constants willy-nilly and deploy
If you are in development mode, running your app on your local lightweight container, then this one is easy to forget. Its good to get into the habit of having a staging environment with Berkeley DB in write-to-disk mode, even on your local, so that you can occasionally get burnt by Exceptions such as this one and so remember it.
java.lang.IllegalArgumentException: Deletion and renaming of enum values is not supported: STANDARD