Design Pattern for storing class/function calls

First of all, sorry could not find a good title :(

Problem
So let's say we have an object and we can apply different actions to manipulate that object and i want to persist this in the database.

As an example, we can define the following classes.

interface IAction{ object transform(object input); }

class Stretch : IAction {  }

class Shrink : IAction {}

And an object can have a list of IAction. Also each action can have a type that we defined.

enum ActionType { Stretch, Shrink }

When we retrieve the actions from the database then we need to do logics to checkh what is the type of the action to know which class to create.

If i just change the order of the items in the enum, then there is nothing that tell me my database has also to change and this can introduce breaking changes.

I'm trying to find a design pattern that will avoid this situation. Is there any?